Uplink transmission cancellation

ABSTRACT

Methods, systems, and devices for wireless communications are described. In some examples, a base station or other network entity may allocate uplink resources to UEs, or groups of UEs, that are subsequently reallocated. For example, a base station may determine a reallocation of uplink resources and issue a cancellation or preemption indication that may correspond to at least a portion of the previously-allocated resources (e.g., as allocated to particular UEs). UEs may be configured to monitor for cancellation or preemption indications, and based on received cancellation or preemption indications, UEs may determine whether or not to proceed with an uplink transmission using their previously-allocated uplink resources.

CROSS REFERENCE

The present application for patent is a Continuation of U.S. patentapplication Ser. No. 16/809,406 by FAKOORIAN et al., entitled “UPLINKTRANSMISSION CANCELLATION” filed Mar. 4, 2020, which claims the benefitof U.S. Provisional Patent Application No. 62/843,198 by FAKOORIAN etal., entitled “UPLINK TRANSMISSION CANCELLATION,” filed May 3, 2019,assigned to the assignee hereof, and expressly incorporated by referenceherein.

TECHNICAL FIELD

The following relates generally to wireless communications, and morespecifically to uplink transmission cancellation.

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be capable ofsupporting communication with multiple users by sharing the availablesystem resources (e.g., time, frequency, and power). Examples of suchmultiple-access systems include fourth generation (4G) systems such asLong Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, orLTE-A Pro systems, and fifth generation (5G) systems which may bereferred to as New Radio (NR) systems. These systems may employtechnologies such as code division multiple access (CDMA), time divisionmultiple access (TDMA), frequency division multiple access (FDMA),orthogonal frequency division multiple access (OFDMA), or discreteFourier transform spread orthogonal frequency division multiplexing(DFT-S-OFDM). A wireless multiple-access communications system mayinclude a number of base stations or network access nodes, eachsimultaneously supporting communication for multiple communicationdevices, which may be otherwise known as user equipment (UE).

Some wireless communications systems, such as NR systems, may supportheterogeneous conditions for one or more service deployments. Forexample, communication devices, such as a base station or a UE, maysupport flexibility in allocating multiple supported services or traffictypes over resources of a channel. As part of the allocation of channelresources, a base station and a UE may support the prioritization ofsome communications over others, which may include prioritization oftraffic or services having different reliability thresholds, differentlatency thresholds, or both. In some cases, efficient system utilizationmay be based on how resources are shared or allocated between differenttraffic types, or UEs configured according to different traffic types.

SUMMARY

The described techniques relate to improved methods, systems, devices,and apparatuses that support uplink transmission cancellation. In someexamples, a base station or other network entity may allocate uplinkresources to UEs, or groups of UEs, that are subsequently reallocated(e.g., based on a reprioritization of communications). For example, abase station may determine a reallocation of uplink resources and issuea cancellation indication that may correspond to at least a portion ofthe previously-allocated resources (e.g., as allocated to particularUEs). UEs may be configured to monitor for cancellation indications, andbased on received cancellation indications, UEs may determine whether ornot to proceed with an uplink transmission using theirpreviously-allocated uplink resources.

In some examples, a cancellation indication may be used to prevent a UEfrom using at least a portion of previously-allocated uplink resourcesfor an uplink transmission, which may support a dynamic allocation ofuplink resources from communications associated with one latencythreshold to communications associated with another latency threshold.For example, resources that were originally allocated to enhanced mobilebroadband (eMBB) communications may be reallocated to ultra-reliablelow-latency communications (URLLC) (e.g., a reallocation towards moreperformance-sensitive communications). In one example, an eMBB UE thatdecodes an uplink cancellation indication message will cancel orotherwise preempt uplink transmission (e.g., partially or completely,depending on whether the uplink cancellation applies to allocatedresources corresponding to the uplink transmission). In some examples, aparticular UE may ignore a cancellation indication, such as when acancellation indication is meant to halt uplink transmissions from otherUEs in order to reallocate the uplink resources to the particular UE, orto a type of traffic that is to be transmitted by the particular UE.Thus, according to these and other examples, various types of uplinkresource allocations may be canceled, preempted, or reallocated, therebysupporting a dynamic redistribution of uplink resources in a wirelesscommunication system that more-effectively balances the performance andresource utilization of communications according to differentpriorities.

A method for wireless communications is described. The method mayinclude identifying an allocation of uplink resources, receiving anuplink cancellation indication, determining whether the identifiedallocation of uplink resources is canceled based on the uplinkcancellation indication, and performing uplink communications based onthe determining.

An apparatus for wireless communications is described. The apparatus mayinclude a processor, memory coupled (e.g., operatively, communicatively,functionally, electronically, electrically) to the processor, andinstructions stored in the memory. The instructions may be executable bythe processor to cause the apparatus to identify an allocation of uplinkresources, receive an uplink cancellation indication, determine whetherthe identified allocation of uplink resources is canceled based on theuplink cancellation indication, and perform uplink communications basedon the determining.

Another apparatus for wireless communications is described. Theapparatus may include means for identifying an allocation of uplinkresources, means for receiving an uplink cancellation indication, meansfor determining whether the identified allocation of uplink resources iscanceled based on the uplink cancellation indication, and means forperforming uplink communications based on the determining.

A non-transitory computer-readable medium storing code for wirelesscommunications is described. The code may include instructionsexecutable by a processor to identify an allocation of uplink resources,receive an uplink cancellation indication, determine whether theidentified allocation of uplink resources is canceled based on theuplink cancellation indication, and perform uplink communications basedon the determining.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the allocation of uplinkresources may be associated with a first type of communications and theuplink cancellation indication may be associated with a second type ofcommunications. In some examples, the first type of communications mayhave a first latency threshold, and the second type of communicationsmay have a second latency threshold that is different from the firstlatency threshold. In some examples, the second type of communicationsmay have a higher priority than the first type of communications. Insome examples, performing the uplink communications may includeperforming uplink communications of either the first type ofcommunications or the second type of communications based on thedetermining

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining whether theidentified allocation of uplink resources is canceled may includeoperations, features, means, or instructions for identifying a bitmap ofthe uplink cancellation indication associated with a set ofcommunication resources in the time domain and frequency domain, eachbit of the bitmap corresponding to a respective subset of thecommunication resources, and each bit indicating whether or notcancellation applies to the respective subset of the communicationresources, and determining whether at least a portion of the allocationof uplink resources corresponds to one or more of the subsets of thecommunication resources for which cancellation applies.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining whether theidentified allocation of uplink resources is canceled may includeoperations, features, means, or instructions for determining that thebitmap corresponds to an uplink bandwidth part configured for the UE.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying arepetition indicator, and repeating bits of the bitmap according to therepetition indicator, each repeated bit of the bitmap corresponding to arespective subset of the communication resources, and each repeated bitindicating whether or not cancellation applies to the respective subsetof the communication resources.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for determining that therespective subset of the communication resources corresponding to eachbit of the bitmap corresponds to uplink resources of an uplink/downlinktime division duplex (TDD) configuration of the UE.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving acancellation configuration, prior to receiving the uplink cancellationindication, associated with a pattern of communication resources in thetime domain and frequency domain, where the uplink cancellationindication indicates a time for applying the pattern of communicationresources for cancellation.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the cancellationconfiguration includes a radio resource control (RRC) configuration.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining whether theidentified allocation of uplink resources is canceled may includeoperations, features, means, or instructions for determining a time forapplying cancellation based on a time of receiving the uplinkcancellation indication and a configured time offset for cancellation.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the configured time offsetfor cancellation may be based on a capability of the UE.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the time forapplying cancellation may be based on an uplink/downlink time divisionduplex (TDD) configuration of the UE.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving an uplinkgrant after receiving the uplink cancellation indication, the uplinkgrant including communication resources associated with the uplinkcancellation indication, and ignoring at least a portion of the uplinkcancellation indication based on receiving the uplink grant afterreceiving the uplink cancellation indication.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the uplink grant may bereceived in a physical downlink control channel (PDCCH).

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, ignoring at least a portionof the uplink cancellation indication may be based on the uplink grantbeing associated with the second type of communications.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, ignoring at least a portionof the uplink cancellation indication may be based on a type of physicalchannel associated with the uplink grant.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining whether theidentified allocation of uplink resources is canceled may be based on atype of physical channel associated with the uplink communications.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining whether theidentified allocation of uplink resources is canceled may be based on atype of physical channel associated with the uplink cancellationindication.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining whether theidentified allocation of uplink resources is canceled may be based on anallocation type associated with the identified allocation of uplinkresources.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining whether theidentified allocation of uplink resources is canceled may be based onthe second type of communications.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining whether theidentified allocation of uplink resources is canceled may be based on atype of communications associated with the uplink communications.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the uplink cancellationindication may be received in a group common physical downlink controlchannel (GC-PDCCH).

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, performing the uplinkcommunications may include operations, features, means, or instructionsfor transmitting an uplink transmission on a subset of the allocation ofuplink resources based on the determining.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, performing the uplinkcommunications may include operations, features, means, or instructionsfor refraining from using at least a portion of the allocation of uplinkresources based on the determining.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the first type ofcommunications includes enhanced mobile broadband (eMBB) communicationsand the second type of communications includes ultra-reliable lowlatency communications (URLLC).

A method for wireless communications is described. The method mayinclude transmitting an allocation of uplink resources, determining areallocation of the uplink resources, and transmitting an uplinkcancellation indication corresponding to the uplink resources based onthe determining.

An apparatus for wireless communications is described. The apparatus mayinclude a processor, memory coupled (e.g., operatively, communicatively,functionally, electronically, electrically) to the processor, andinstructions stored in the memory. The instructions may be executable bythe processor to cause the apparatus to transmit an allocation of uplinkresources, determine a reallocation of the uplink resources, andtransmit an uplink cancellation indication corresponding to the uplinkresources based on the determining.

Another apparatus for wireless communications is described. Theapparatus may include means for transmitting an allocation of uplinkresources, means for determining a reallocation of the uplink resources,and means for transmitting an uplink cancellation indicationcorresponding to the uplink resources based on the determining.

A non-transitory computer-readable medium storing code for wirelesscommunications is described. The code may include instructionsexecutable by a processor to transmit an allocation of uplink resources,determine a reallocation of the uplink resources, and transmit an uplinkcancellation indication corresponding to the uplink resources based onthe determining.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the allocation of uplinkresources may be associated with a first type of communications anddetermining the reallocation of the uplink resources may be based on asecond type of communications. In some examples, the first type ofcommunications may have a first latency threshold, and the second typeof communications may have a second latency threshold that is differentfrom the first latency threshold. In some examples, the second type ofcommunications may have a higher priority than the first type ofcommunications.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for generating a bitmapassociated with a set of communication resources in the time domain andfrequency domain, each bit of the bitmap corresponding to a respectivesubset of the communication resources, and each bit indicating whetheror not cancellation applies to the respective subset of thecommunication resources, and transmitting the uplink cancellationindication may include transmitting the bitmap.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the bitmap corresponds to aconfigured uplink bandwidth part.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, transmitting the uplinkcancellation indication may include operations, features, means, orinstructions for transmitting a repetition indicator associated with thebitmap.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the respective subset of thecommunication resources corresponding to each bit of the bitmapcorresponds to uplink resources of an uplink/downlink TDD configuration.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for transmitting acancellation configuration, prior to transmitting the uplinkcancellation indication, associated with a pattern of communicationresources in the time domain and frequency domain, and the uplinkcancellation indication may indicate a time for applying the pattern ofcommunication resources for cancellation.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, transmitting the cancellationconfiguration may include operations, features, means, or instructionsfor transmitting an RRC configuration.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the reallocationof resources may include operations, features, means, or instructionsfor determining a time for applying cancellation based on a time oftransmitting the uplink cancellation indication and a configured timeoffset for cancellation.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the configured time offsetfor cancellation may be based on a UE capability.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the time forapplying cancellation may be based on an uplink/downlink time divisionduplex (TDD) configuration.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for transmitting, to a UE,an uplink grant including communication resources associated with theuplink cancellation indication, the uplink grant indicating to the UE toignore at least a portion of the uplink cancellation indication.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the uplink grant may betransmitted in a physical downlink control channel (PDCCH).

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the uplink grant may beassociated with the second type of communications, and the indication tothe UE to ignore at least a portion of the uplink cancellationindication may be based on the uplink grant being associated with thesecond type of communications.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the uplink grant may beassociated with a type of physical channel, and the indication to the UEto ignore at least a portion of the uplink cancellation indication maybe based on the type of physical channel.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the reallocationof the uplink resources may include operations, features, means, orinstructions for determining a reallocation of uplink resourcesallocated to a physical random access channel (PRACH) based at least inpart on a triggering condition for transmissions associated with theuplink resources allocated to the PRACH.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the uplink cancellationindication may be specific to a type of uplink physical channel.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the uplink cancellationindication may be specific to a type of uplink resource allocation.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, transmitting the uplinkcancellation indication may include operations, features, means, orinstructions for transmitting a group common physical downlink controlchannel (GC-PDCCH).

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receivingcommunications from one or more user equipments (UEs) based on thereallocation of the uplink resources and transmitting the uplinkcancellation indication.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the first type ofcommunications includes enhanced mobile broadband (eMBB) communicationsand the second type of communications includes ultra-reliable lowlatency communications (URLLC).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a system for wireless communicationsthat supports uplink transmission cancellation in accordance withaspects of the present disclosure.

FIG. 2 illustrates an example of a system for wireless communicationsthat supports uplink transmission cancellation in accordance withaspects of the present disclosure.

FIGS. 3A and 3B illustrate examples for mapping a bitfield of an uplinkcancellation indication to communication resources for uplinktransmission cancellation in accordance with the present disclosure.

FIGS. 4A and 4B illustrate examples of processing timelines thatsupports uplink transmission cancellation in accordance with aspects ofthe present disclosure.

FIG. 5 illustrates an example of a wireless communications system andcorresponding operations that support uplink transmission cancellationin accordance with aspects of the present disclosure.

FIGS. 6 and 7 show block diagrams of devices that support uplinktransmission cancellation in accordance with aspects of the presentdisclosure.

FIG. 8 shows a block diagram of a communication manager that supportsuplink transmission cancellation in accordance with aspects of thepresent disclosure.

FIG. 9 shows a diagram of a system including a device that supportsuplink transmission cancellation in accordance with aspects of thepresent disclosure.

FIGS. 10 and 11 show block diagrams of devices that support uplinktransmission cancellation in accordance with aspects of the presentdisclosure.

FIG. 12 shows a block diagram of a communication manager that supportsuplink transmission cancellation in accordance with aspects of thepresent disclosure.

FIG. 13 shows a diagram of a system including a device that supportsuplink transmission cancellation in accordance with aspects of thepresent disclosure.

FIGS. 14 through 17 show flowcharts illustrating methods that supportuplink transmission cancellation in accordance with aspects of thepresent disclosure.

DETAILED DESCRIPTION

Some communication systems may support different traffic types (e.g.,traffic categories), which may include or refer to communicationstraffic having different reliability thresholds, different latencythresholds, different services, or various combinations thereof. Forexample, a wireless communication system may support a first traffictype (e.g., communications type), associated with relatively highreliability targets or thresholds and relatively low latency targets orthresholds, such as ultra-reliable low-latency communications (URLLC)traffic type. The wireless communication system may also support asecond traffic type, associated with relatively low reliability targetsor thresholds and relatively long or relaxed latency thresholds, such asenhanced mobile broadband (eMBB) traffic type. In some cases, to supportvarious system operations (e.g., efficient utilization of wirelesscommunication resources, appropriate allocation or balancing of wirelesscommunication resources, appropriate support of traffic according todifferent prioritization or latency threshold), a wireless communicationsystem may support dynamic resource sharing between traffic types, suchas a dynamic allocation of resources between URLLC communications andeMBB communications, or other communications, according to differenttraffic types, categories, or other prioritizations.

The described techniques include various examples of dynamic resourceallocation by way of cancellation or preemption of previously-allocateduplink resources by a network entity, such as a base station or othercontroller or resource allocation authority in communication with a basestation. For example, a base station, or other network entity, mayallocate uplink resources (e.g., an initial uplink resource allocation)to UEs, or groups of UEs, and the base station may subsequently issue acancellation or preemption indication (e.g., an uplink allocationcancellation indication) that may correspond to at least a portion ofthe previously-allocated uplink resources (e.g., as allocated toparticular UEs). UEs may detect such a cancellation indication, anddetermine whether or not to proceed with an uplink transmission usingtheir previously-allocated uplink resources.

In some examples, a cancellation indication may be used to prevent a UEfrom using at least a portion of previously-allocated uplink resourcesfor an uplink transmission, which may support a dynamic allocation ofuplink resources from communications associated with one latencythreshold to communications associated with another latency threshold,or some other reallocation based on communications prioritization. Forexample, resources that were originally allocated to eMBB communicationsmay be reallocated to URLLC communications (e.g., a reallocation towardsmore performance-sensitive communications). In some examples, aparticular UE may ignore a cancellation indication, such as when acancellation indication is meant to halt uplink transmissions from otherUEs in order to reallocate the uplink resources to the particular UE, orto a type of traffic that is to be transmitted by the particular UE.Thus, according to these and other examples, various types of uplinkresource allocations may be canceled, preempted, or reallocated, therebysupporting a dynamic redistribution of uplink resources in a wirelesscommunication system that more-effectively balances the performance andresource utilization of communications according to differentpriorities.

Aspects of the disclosure are initially described in the context of awireless communications system. Aspects of the disclosure are furtherillustrated by and described with reference to examples of signaling,operations, and resource mapping that may support the describedtechniques for uplink transmission cancellation. Aspects of thedisclosure are further illustrated by and described with reference toapparatus diagrams, system diagrams, and flowcharts that relate touplink transmission cancellation.

FIG. 1 illustrates an example of a wireless communications system 100that supports uplink transmission cancellation in accordance withaspects of the present disclosure. The wireless communications system100 includes base stations 105, UEs 115, and a core network 130. In someexamples, the wireless communications system 100 may be a Long TermEvolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pronetwork, or a New Radio (NR) network. In some cases, wirelesscommunications system 100 may support enhanced broadband communications,ultra-reliable (e.g., mission critical) communications, low latencycommunications, or communications with low-cost and low-complexitydevices.

Base stations 105 may wirelessly communicate with UEs 115 via one ormore base station antennas. Base stations 105 described herein mayinclude or may be referred to by those skilled in the art as a basetransceiver station, a radio base station, an access point, a radiotransceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB orgiga-NodeB (either of which may be referred to as a gNB), a Home NodeB,a Home eNodeB, or some other suitable terminology. Wirelesscommunications system 100 may include base stations 105 of differenttypes (e.g., macro or small cell base stations). The UEs 115 describedherein may be able to communicate with various types of base stations105 and network equipment including macro eNBs, small cell eNBs, gNBs,relay base stations, and the like.

Each base station 105 may be associated with a particular geographiccoverage area 110 in which communications with various UEs 115 issupported. Each base station 105 may provide communication coverage fora respective geographic coverage area 110 via communication links 125,and communication links 125 between a base station 105 and a UE 115 mayutilize one or more carriers. Communication links 125 shown in wirelesscommunications system 100 may include uplink transmissions from a UE 115to a base station 105, or downlink transmissions from a base station 105to a UE 115. Downlink transmissions may also be called forward linktransmissions while uplink transmissions may also be called reverse linktransmissions.

The geographic coverage area 110 for a base station 105 may be dividedinto sectors making up a portion of the geographic coverage area 110,and each sector may be associated with a cell. For example, each basestation 105 may provide communication coverage for a macro cell, a smallcell, a hot spot, or other types of cells, or various combinationsthereof. In some examples, a base station 105 may be movable andtherefore provide communication coverage for a moving geographiccoverage area 110. In some examples, different geographic coverage areas110 associated with different technologies may overlap, and overlappinggeographic coverage areas 110 associated with different technologies maybe supported by the same base station 105 or by different base stations105. The wireless communications system 100 may include, for example, aheterogeneous LTE/LTE-A/LTE-A Pro or NR network in which different typesof base stations 105 provide coverage for various geographic coverageareas 110.

The term “cell” refers to a logical communication entity used forcommunication with a base station 105 (e.g., over a carrier), and may beassociated with an identifier for distinguishing neighboring cells(e.g., a physical cell identifier (PCID), a virtual cell identifier(VCID)) operating via the same or a different carrier. In some examples,a carrier may support multiple cells, and different cells may beconfigured according to different protocol types (e.g., machine-typecommunication (MTC), narrowband Internet-of-Things (NB-IoT), enhancedmobile broadband (eMBB), or others) that may provide access fordifferent types of devices. In some cases, the term “cell” may refer toa portion of a geographic coverage area 110 (e.g., a sector) over whichthe logical entity operates.

UEs 115 may be dispersed throughout the wireless communications system100, and each UE 115 may be stationary or mobile. A UE 115 may also bereferred to as a mobile device, a wireless device, a remote device, ahandheld device, or a subscriber device, or some other suitableterminology, where the “device” may also be referred to as a unit, astation, a terminal, or a client. A UE 115 may be a device such as acellular phone, a smart phone, a personal digital assistant (PDA), amultimedia/entertainment device (e.g., a radio, a MP3 player, a videodevice, etc.), a camera, a gaming device, a navigation/positioningdevice (e.g., GNSS (global navigation satellite system) devices basedon, for example, GPS (global positioning system), Beidou, GLONASS, orGalileo, a terrestrial-based device, etc.), a tablet computer, a laptopcomputer, a netbook, a smartbook, a personal computer, a smart device, awearable device (e.g., a smart watch, smart clothing, smart glasses,virtual reality goggles, a smart wristband, smart jewelry (e.g., a smartring, a smart bracelet)), a drone, a robot/robotic device, a vehicle, avehicular device, a meter (e.g., parking meter, electric meter, gasmeter, water meter), a monitor, a gas pump, an appliance (e.g., kitchenappliance, washing machine, dryer), a location tag, a medical/healthcaredevice, an implant, a sensor/actuator, a display, or any other suitabledevice configured to communicate via a wireless or wired medium. In someexamples, a UE 115 may also refer to a wireless local loop (WLL)station, an Internet of Things (IoT) device, an Internet of Everything(IoE) device, or an MTC device, or the like, which may be implemented invarious articles such as appliances, drones, robots, vehicles, meters,or the like

Some UEs 115, such as MTC or IoT devices, may be low cost or lowcomplexity devices, and may provide for automated communication betweenmachines (e.g., via Machine-to-Machine (M2M) communication). M2Mcommunication or MTC may refer to data communication technologies thatallow devices to communicate with one another or a base station 105without human intervention. In some examples, M2M communication or MTCmay include communications from devices that integrate sensors or metersto measure or capture information and relay that information to acentral server or application program that can make use of theinformation or present the information to humans interacting with theprogram or application. Some UEs 115 may be designed to collectinformation or enable automated behavior of machines. Examples ofapplications for MTC devices include smart metering, inventorymonitoring, water level monitoring, equipment monitoring, healthcaremonitoring, wildlife monitoring, weather and geological eventmonitoring, fleet management and tracking, remote security sensing,physical access control, and transaction-based business charging. In anaspect, techniques disclosed herein may be applicable to MTC or IoT UEs.MTC or IoT UEs may include MTC/enhanced MTC (eMTC, also referred to asCAT-M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, as well asother types of UEs. eMTC and NB-IoT may refer to future technologiesthat may evolve from or may be based on these technologies. For example,eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC),mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhancedNB-IoT), FeNB-IoT (further enhanced NB-IoT), etc.

Some UEs 115 may be configured to employ operating modes that reducepower consumption, such as half-duplex communications (e.g., a mode thatsupports one-way communication via transmission or reception, but nottransmission and reception simultaneously). In some examples,half-duplex communications may be performed at a reduced peak rate.Other power conservation techniques for UEs 115 include entering a powersaving “deep sleep” mode when not engaging in active communications, oroperating over a limited bandwidth (e.g., according to narrowbandcommunications). In some cases, UEs 115 may be designed to supportcritical functions (e.g., mission critical functions), and a wirelesscommunications system 100 may be configured to provide ultra-reliablecommunications for these functions.

In some cases, a UE 115 may also be able to communicate directly withother UEs 115 (e.g., using a peer-to-peer (P2P) or device-to-device(D2D) protocol). One or more of a group of UEs 115 utilizing D2Dcommunications may be within the geographic coverage area 110 of a basestation 105. Other UEs 115 in such a group may be outside the geographiccoverage area 110 of a base station 105, or be otherwise unable toreceive transmissions from a base station 105. In some cases, groups ofUEs 115 communicating via D2D communications may utilize a one-to-many(1:M) system in which each UE 115 transmits to every other UE 115 in thegroup. In some cases, a base station 105 facilitates the scheduling ofresources for D2D communications. In other cases, D2D communications arecarried out between UEs 115 without the involvement of a base station105.

Base stations 105 may communicate with the core network 130 and with oneanother. For example, base stations 105 may interface with the corenetwork 130 through backhaul links 132 (e.g., via an S1, N2, N3, orother interface). Base stations 105 may communicate with one anotherover backhaul links 134 (e.g., via an X2, Xn, or other interface) eitherdirectly (e.g., directly between base stations 105) or indirectly (e.g.,via core network 130).

The core network 130 may provide user authentication, accessauthorization, tracking, Internet Protocol (IP) connectivity, and otheraccess, routing, or mobility functions. The core network 130 may be anevolved packet core (EPC), which may include at least one mobilitymanagement entity (MME), at least one serving gateway (S-GW), and atleast one Packet Data Network (PDN) gateway (P-GW). The MME may managenon-access stratum (e.g., control plane) functions such as mobility,authentication, and bearer management for UEs 115 served by basestations 105 associated with the EPC. User IP packets may be transferredthrough the S-GW, which itself may be connected to the P-GW. The P-GWmay provide IP address allocation as well as other functions. The P-GWmay be connected to the network operators IP services. The operators IPservices may include access to the Internet, Intranet(s), an IPMultimedia Subsystem (IMS), or a Packet-Switched (PS) Streaming Service.

At least some of the network devices, such as a base station 105, mayinclude subcomponents such as an access network entity, which may be anexample of an access node controller (ANC). Each access network entitymay communicate with UEs 115 through a number of other access networktransmission entities, which may be referred to as a radio head, a smartradio head, or a transmission/reception point (TRP). In someconfigurations, various functions of each access network entity or basestation 105 may be distributed across various network devices (e.g.,radio heads and access network controllers) or consolidated into asingle network device (e.g., a base station 105).

Wireless communications system 100 may operate using one or morefrequency bands, typically in the range of 300 megahertz (MHz) to 300gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known asthe ultra-high frequency (UHF) region or decimeter band, since thewavelengths range from approximately one decimeter to one meter inlength. UHF waves may be blocked or redirected by buildings andenvironmental features. However, the waves may penetrate structuressufficiently for a macro cell to provide service to UEs 115 locatedindoors. Transmission of UHF waves may be associated with smallerantennas and shorter range (e.g., less than 100 km) compared totransmission using the smaller frequencies and longer waves of the highfrequency (HF) or very high frequency (VHF) portion of the spectrumbelow 300 MHz.

Wireless communications system 100 may also operate in a super highfrequency (SHF) region using frequency bands from 3 GHz to 30 GHz, alsoknown as the centimeter band. The SHF region includes bands such as the5 GHz industrial, scientific, and medical (ISM) bands, which may be usedopportunistically by devices that may be capable of toleratinginterference from other users.

Wireless communications system 100 may also operate in an extremely highfrequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz),also known as the millimeter band. In some examples, wirelesscommunications system 100 may support millimeter wave (mmW)communications between UEs 115 and base stations 105, and EHF antennasof the respective devices may be even smaller and more closely spacedthan UHF antennas. In some cases, this may facilitate use of antennaarrays within a UE 115. However, the propagation of EHF transmissionsmay be subject to even greater atmospheric attenuation and shorter rangethan SHF or UHF transmissions. Techniques disclosed herein may beemployed across transmissions that use one or more different frequencyregions, and designated use of bands across these frequency regions maydiffer by country or regulating body.

In some cases, wireless communications system 100 may utilize bothlicensed and unlicensed radio frequency spectrum bands. For example,wireless communications system 100 may employ License Assisted Access(LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technologyin an unlicensed band such as the 5 GHz ISM band. When operating inunlicensed radio frequency spectrum bands, wireless devices such as basestations 105 and UEs 115 may employ listen-before-talk (LBT) proceduresto ensure a frequency channel is clear before transmitting data. In somecases, operations in unlicensed bands may be based on a carrieraggregation configuration in conjunction with component carriersoperating in a licensed band (e.g., LAA). Operations in unlicensedspectrum may include downlink transmissions, uplink transmissions,peer-to-peer transmissions, or a combination of these. Duplexing inunlicensed spectrum may be based on frequency division duplexing (FDD),time division duplexing (TDD), or a combination of both.

In some examples, base station 105 or UE 115 may be equipped withmultiple antennas, which may be used to employ techniques such astransmit diversity, receive diversity, multiple-input multiple-output(MIMO) communications, or beamforming. For example, wirelesscommunications system 100 may use a transmission scheme between atransmitting device (e.g., a base station 105) and a receiving device(e.g., a UE 115), where the transmitting device is equipped withmultiple antennas and the receiving device is equipped with one or moreantennas. MIMO communications may employ multipath signal propagation toincrease the spectral efficiency by transmitting or receiving multiplesignals via different spatial layers, which may be referred to asspatial multiplexing. The multiple signals may, for example, betransmitted by the transmitting device via different antennas ordifferent combinations of antennas. Likewise, the multiple signals maybe received by the receiving device via different antennas or differentcombinations of antennas. Each of the multiple signals may be referredto as a separate spatial stream, and may carry bits associated with thesame data stream (e.g., the same codeword) or different data streams.Different spatial layers may be associated with different antenna portsused for channel measurement and reporting. MIMO techniques includesingle-user MIMO (SU-MIMO) where multiple spatial layers are transmittedto the same receiving device, and multiple-user MIMO (MU-MIMO) wheremultiple spatial layers are transmitted to multiple devices.

Beamforming, which may also be referred to as spatial filtering,directional transmission, or directional reception, is a signalprocessing technique that may be used at a transmitting device or areceiving device (e.g., a base station 105 or a UE 115) to shape orsteer an antenna beam (e.g., a transmit beam or receive beam) along aspatial path between the transmitting device and the receiving device.Beamforming may be achieved by combining the signals communicated viaantenna elements of an antenna array such that signals propagating atparticular orientations with respect to an antenna array experienceconstructive interference while others experience destructiveinterference. The adjustment of signals communicated via the antennaelements may include a transmitting device or a receiving deviceapplying certain amplitude and phase offsets to signals carried via eachof the antenna elements associated with the device. The adjustmentsassociated with each of the antenna elements may be defined by abeamforming weight set associated with a particular orientation (e.g.,with respect to the antenna array of the transmitting device orreceiving device, or with respect to some other orientation).

In one example, a base station 105 may use multiple antennas or antennaarrays to conduct beamforming operations for directional communicationswith a UE 115. For instance, some signals (e.g., synchronizationsignals, reference signals, beam selection signals, or other controlsignals) may be transmitted by a base station 105 multiple times indifferent directions, which may include a signal being transmittedaccording to different beamforming weight sets associated with differentdirections of transmission. Transmissions in different beam directionsmay be used to identify (e.g., by the base station 105 or a receivingdevice, such as a UE 115) a beam direction for subsequent transmissionand/or reception by the base station 105.

Some signals, such as data signals associated with a particularreceiving device, may be transmitted by a base station 105 in a singlebeam direction (e.g., a direction associated with the receiving device,such as a UE 115). In some examples, the beam direction associated withtransmissions along a single beam direction may be determined based atleast in in part on a signal that was transmitted in different beamdirections. For example, a UE 115 may receive one or more of the signalstransmitted by the base station 105 in different directions, and the UE115 may report to the base station 105 an indication of the signal itreceived with a highest signal quality, or an otherwise acceptablesignal quality. Although these techniques are described with referenceto signals transmitted in one or more directions by a base station 105,a UE 115 may employ similar techniques for transmitting signals multipletimes in different directions (e.g., for identifying a beam directionfor subsequent transmission or reception by the UE 115), or transmittinga signal in a single direction (e.g., for transmitting data to areceiving device).

A receiving device (e.g., a UE 115, which may be an example of a mmWreceiving device) may try multiple receive beams when receiving varioussignals from the base station 105, such as synchronization signals,reference signals, beam selection signals, or other control signals. Forexample, a receiving device may try multiple receive directions byreceiving via different antenna subarrays, by processing receivedsignals according to different antenna subarrays, by receiving accordingto different receive beamforming weight sets applied to signals receivedat a plurality of antenna elements of an antenna array, or by processingreceived signals according to different receive beamforming weight setsapplied to signals received at a plurality of antenna elements of anantenna array, any of which may be referred to as “listening” accordingto different receive beams or receive directions. In some examples, areceiving device may use a single receive beam to receive along a singlebeam direction (e.g., when receiving a data signal). The single receivebeam may be aligned in a beam direction determined based at least inpart on listening according to different receive beam directions (e.g.,a beam direction determined to have a highest signal strength, highestsignal-to-noise ratio, or otherwise acceptable signal quality based atleast in part on listening according to multiple beam directions).

In some cases, the antennas of a base station 105 or UE 115 may belocated within one or more antenna arrays, which may support MIMOoperations, or transmit or receive beamforming. For example, one or morebase station antennas or antenna arrays may be co-located at an antennaassembly, such as an antenna tower. In some cases, antennas or antennaarrays associated with a base station 105 may be located in diversegeographic locations. A base station 105 may have an antenna array witha number of rows and columns of antenna ports that the base station 105may use to support beamforming of communications with a UE 115.Likewise, a UE 115 may have one or more antenna arrays that may supportvarious MIMO or beamforming operations.

In some cases, wireless communications system 100 may be a packet-basednetwork that operate according to a layered protocol stack. In the userplane, communications at the bearer or Packet Data Convergence Protocol(PDCP) layer may be IP-based. A Radio Link Control (RLC) layer mayperform packet segmentation and reassembly to communicate over logicalchannels. A Medium Access Control (MAC) layer may perform priorityhandling and multiplexing of logical channels into transport channels.The MAC layer may also use hybrid automatic repeat request (HARQ) toprovide retransmission at the MAC layer to improve link efficiency. Inthe control plane, the Radio Resource Control (RRC) protocol layer mayprovide establishment, configuration, and maintenance of an RRCconnection between a UE 115 and a base station 105 or core network 130supporting radio bearers for user plane data. At the Physical layer,transport channels may be mapped to physical channels.

In some cases, UEs 115 and base stations 105 may support retransmissionsof data to increase the likelihood that data is received successfully.HARQ feedback is one technique of increasing the likelihood that data isreceived correctly over a communication link 125. HARQ may include acombination of error detection (e.g., using a cyclic redundancy check(CRC)), forward error correction (FEC), and retransmission (e.g.,automatic repeat request (ARQ)). HARQ may improve throughput at the MAClayer in poor radio conditions (e.g., signal-to-noise conditions). Insome cases, a wireless device may support same-slot HARQ feedback, wherethe device may provide HARQ feedback in a specific slot for datareceived in a previous symbol in the slot. In other cases, the devicemay provide HARQ feedback in a subsequent slot, or according to someother time interval.

Time intervals in LTE or NR may be expressed in multiples of a basictime unit, which may, for example, refer to a sampling period ofT_(s)=1/30,720,000 seconds. Time intervals of a communications resourcemay be organized according to radio frames each having a duration of 10milliseconds (ms), where the frame period may be expressed asT_(f)=307,200 T_(s). The radio frames may be identified by a systemframe number (SFN) ranging from 0 to 1023. Each frame may include 10subframes numbered from 0 to 9, and each subframe may have a duration of1 ms. A subframe may be further divided into 2 slots each having aduration of 0.5 ms, and each slot may contain 6 or 7 modulation symbolperiods (e.g., depending on the length of the cyclic prefix prepended toeach symbol period). Excluding the cyclic prefix, each symbol period maycontain 2048 sampling periods. In some cases, a subframe may be thesmallest scheduling unit of the wireless communications system 100, andmay be referred to as a transmission time interval (TTI). In othercases, a smallest scheduling unit of the wireless communications system100 may be shorter than a subframe or may be dynamically selected (e.g.,in bursts of shortened TTIs (sTTIs) or in selected component carriersusing sTTIs).

In some wireless communications systems, a slot may further be dividedinto multiple mini-slots containing one or more symbols. In someinstances, a symbol of a mini-slot or a mini-slot may be the smallestunit of scheduling. Each symbol may vary in duration depending on thesubcarrier spacing or frequency band of operation, for example. Further,some wireless communications systems may implement slot aggregation inwhich multiple slots or mini-slots are aggregated together and used forcommunication between a UE 115 and a base station 105.

The term “carrier” refers to a set of radio frequency spectrum resourceshaving a defined physical layer structure for supporting communicationsover a communication link 125. For example, a carrier of a communicationlink 125 may include a portion of a radio frequency spectrum band thatis operated according to physical layer channels for a given radioaccess technology. Each physical layer channel may carry user data,control information, or other signaling. A carrier may be associatedwith a pre-defined frequency channel (e.g., an evolved universal mobiletelecommunication system terrestrial radio access (E-UTRA) absoluteradio frequency channel number (EARFCN)), and may be positionedaccording to a channel raster for discovery by UEs 115. Carriers may bedownlink or uplink (e.g., in an FDD mode), or be configured to carrydownlink and uplink communications (e.g., in a TDD mode). In someexamples, signal waveforms transmitted over a carrier may be made up ofmultiple sub-carriers (e.g., using multi-carrier modulation (MCM)techniques such as orthogonal frequency division multiplexing (OFDM) ordiscrete Fourier transform spread OFDM (DFT-S-OFDM)).

The organizational structure of the carriers may be different fordifferent radio access technologies (e.g., LTE, LTE-A, LTE-A Pro, NR).For example, communications over a carrier may be organized according toTTIs or slots, each of which may include user data as well as controlinformation or signaling to support decoding the user data. A carriermay also include dedicated acquisition signaling (e.g., synchronizationsignals or system information, etc.) and control signaling thatcoordinates operation for the carrier. In some examples (e.g., in acarrier aggregation configuration), a carrier may also have acquisitionsignaling or control signaling that coordinates operations for othercarriers.

Physical channels may be multiplexed on a carrier according to varioustechniques. A physical control channel and a physical data channel maybe multiplexed on a downlink carrier, for example, using time divisionmultiplexing (TDM) techniques, frequency division multiplexing (FDM)techniques, or hybrid TDM-FDM techniques. In some examples, controlinformation transmitted in a physical control channel may be distributedbetween different control regions in a cascaded manner (e.g., between acommon control region or common search space and one or more UE-specificcontrol regions or UE-specific search spaces).

A carrier may be associated with a particular bandwidth of the radiofrequency spectrum, and, in some examples, the carrier bandwidth may bereferred to as a “system bandwidth” of the carrier or the wirelesscommunications system 100. For example, the carrier bandwidth may be oneof a number of predetermined bandwidths for carriers of a particularradio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). Insome examples, each served UE 115 may be configured for operating overportions or all of the carrier bandwidth. In other examples, some UEs115 may be configured for operation using a narrowband protocol typethat is associated with a predefined portion or range (e.g., set ofsubcarriers or RBs) within a carrier (e.g., “in-band” deployment of anarrowband protocol type).

In a system employing MCM techniques, a resource element may consist ofone symbol period (e.g., a duration of one modulation symbol) and onesubcarrier, where the symbol period and subcarrier spacing are inverselyrelated. The number of bits carried by each resource element may dependon the modulation scheme (e.g., the order of the modulation scheme).Thus, the more resource elements that a UE 115 receives and the higherthe order of the modulation scheme, the higher the data rate may be forthe UE 115. In MIMO systems, a wireless communications resource mayrefer to a combination of a radio frequency spectrum resource, a timeresource, and a spatial resource (e.g., spatial layers), and the use ofmultiple spatial layers may further increase the data rate forcommunications with a UE 115.

Devices of the wireless communications system 100 (e.g., base stations105 or UEs 115) may have a hardware configuration that supportscommunications over a particular carrier bandwidth, or may beconfigurable to support communications over one of a set of carrierbandwidths. In some examples, the wireless communications system 100 mayinclude base stations 105 and/or UEs 115 that support simultaneouscommunications via carriers associated with more than one differentcarrier bandwidth.

Wireless communications system 100 may support communication with a UE115 on multiple cells or carriers, a feature which may be referred to ascarrier aggregation or multi-carrier operation. A UE 115 may beconfigured with multiple downlink component carriers and one or moreuplink component carriers according to a carrier aggregationconfiguration. Carrier aggregation may be used with both FDD and TDDcomponent carriers.

In some cases, wireless communications system 100 may utilize enhancedcomponent carriers (eCCs). An eCC may be characterized by one or morefeatures including wider carrier or frequency channel bandwidth, shortersymbol duration, shorter TTI duration, or modified control channelconfiguration. In some cases, an eCC may be associated with a carrieraggregation configuration or a dual connectivity configuration (e.g.,when multiple serving cells have a suboptimal or non-ideal backhaullink). An eCC may also be configured for use in unlicensed spectrum orshared spectrum (e.g., where more than one operator is allowed to usethe spectrum). An eCC characterized by wide carrier bandwidth mayinclude one or more segments that may be utilized by UEs 115 that arenot capable of monitoring the whole carrier bandwidth or are otherwiseconfigured to use a limited carrier bandwidth (e.g., to conserve power).

In some cases, an eCC may utilize a different symbol duration than othercomponent carriers, which may include use of a reduced symbol durationas compared with symbol durations of the other component carriers. Ashorter symbol duration may be associated with increased spacing betweenadjacent subcarriers. A device, such as a UE 115 or base station 105,utilizing eCCs may transmit wideband signals (e.g., according tofrequency channel or carrier bandwidths of 20, 40, 60, 80 MHz, etc.) atreduced symbol durations (e.g., 16.67 microseconds). A TTI in eCC mayconsist of one or multiple symbol periods. In some cases, the TTIduration (that is, the number of symbol periods in a TTI) may bevariable.

Wireless communications system 100 may be an NR system that may utilizeany combination of licensed, shared, and unlicensed spectrum bands,among others. The flexibility of eCC symbol duration and subcarrierspacing may allow for the use of eCC across multiple spectrums. In someexamples, NR shared spectrum may increase spectrum utilization andspectral efficiency, specifically through dynamic vertical (e.g., acrossthe frequency domain) and horizontal (e.g., across the time domain)sharing of resources.

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be multiple-accesssystems capable of supporting communication with multiple users bysharing the available system resources (e.g., time, frequency, andpower). A wireless network, for example a wireless local area network(WLAN), such as a Wi-Fi (i.e., Institute of Electrical and ElectronicsEngineers (IEEE) 802.11) network may include an access point (AP) thatmay communicate with one or more wireless or mobile devices. The AP maybe coupled to a network, such as the Internet, and may enable a mobiledevice to communicate via the network (or communicate with other devicescoupled to the access point). A wireless device may communicate with anetwork device bi-directionally. For example, in a WLAN, a device maycommunicate with an associated AP via downlink (e.g., the communicationlink from the AP to the device) and uplink (e.g., the communication linkfrom the device to the AP). A wireless personal area network (PAN),which may include a Bluetooth connection, may provide for short rangewireless connections between two or more paired wireless devices. Forexample, wireless devices such as cellular phones may utilize wirelessPAN communications to exchange information such as audio signals withwireless headsets. Components within a wireless communication system maybe coupled (for example, operatively, communicatively, functionally,electronically, and/or electrically) to each other.

The wireless communications system 100 may be configured to supportdifferent traffic types (e.g., traffic categories, traffic priorities,service priorities), which may include or refer to communicationstraffic having different reliability thresholds, different latencythresholds, different services, or various combinations thereof. Forexample, the wireless communications system 100 may support a firsttraffic type (e.g., communications type), associated with relativelyhigh reliability targets or thresholds and relatively low latencytargets or thresholds, such as ultra-reliable low-latency communications(URLLC) traffic type. The wireless communications system 100 may alsosupport a second traffic type, associated with relatively lowreliability targets or thresholds and relatively long or relaxed latencythresholds, such an enhanced mobile broadband (eMBB) traffic type. Insome cases, to support various system operations (e.g., efficientutilization of wireless communication resources, appropriate allocationor balancing of wireless communication resources, appropriate support oftraffic according to different prioritization or latency threshold), thewireless communications system 100 may support dynamic resource sharingbetween traffic types, such as a dynamic allocation of resources betweenURLLC communications and eMBB communications, or other communications,according to different traffic types, categories, or otherprioritization.

To support various uplink resource allocation techniques, a base station105 or other network entity (e.g., an entity of the core network 130, anentity of a distributed base station 105) may allocate uplink resources(e.g., an initial uplink resource allocation) to UEs 115, or groups ofUEs 115, for uplink transmissions. In some examples, a base station 105or other network entity may subsequently determine to perform areallocation of the previously-allocated uplink resources, which may betriggered, for example, by a determined or detected need, demand, orrequest to support higher-priority communications. Thus, a base station105 or other network entity may generate and transmit an uplinkcancellation indication (ULCI) that may correspond to at least a portionof the previously-allocated uplink resources (e.g., as allocated toparticular UEs 115). UEs 115 may be configured to monitor for ULCIs, andaccordingly may determine, based at least in part on received, detected,or decoded ULCIs, whether or not to proceed with uplink transmissionsusing their previously-allocated uplink resources.

In some examples, ULCI may be used to prevent a UE 115 from using atleast a portion of previously-allocated uplink resources for an uplinktransmission, which may support a dynamic allocation of uplink resourcesfrom communications associated with one latency threshold tocommunications associated with another latency threshold, or some otherreallocation based on communications prioritization. For example,resources that were originally allocated to the UE 115 for eMBBcommunications (e.g., allocated to eMBB UEs, allocated to UEs 115configured for eMBB communications) may be reallocated to the same UE115, or a different UE 115, for URLLC communications (e.g., areallocation towards more performance-sensitive communications). In someexamples, a particular UE 115 may ignore a ULCI, such as when a ULCI ismeant to halt uplink transmissions from other UEs 115 in order toreallocate the uplink resources to the particular UE 115, or to a typeof traffic that is to be transmitted by the particular UE 115. Thus,according to these and other examples, various types of uplink resourceallocations may be canceled, preempted, or reallocated, such that thewireless communications system 100 may support a more dynamicredistribution of uplink resources according to different priorities ofcommunications.

FIG. 2 illustrates an example of a wireless communications system 200that supports uplink transmission cancellation in accordance withaspects of the present disclosure. The wireless communications system200 may include a base station 105-a that supports communication withmultiple UEs (e.g., UE 115-a and UE 115-b) within a supported geographiccoverage area 110-a. In some examples, the communication may supportmission critical applications that include stringent communicationperformance (e.g., reliability thresholds, latency thresholds) alongwith communications of other types. Wireless communications system 200may implement aspects of wireless communications system 100, asdescribed with reference to FIG. 1.

In the wireless communications system 200, UE 115-a and UE 115-b maysupport different service deployments, such as URLLC service and eMBBservice. For example, the UE 115-a may support URLLC transmission toreduce end-to-end latency for data transmission and reception associatedwith the base station 105-a. In some examples, the UE 115-a maycorrespond to a URLLC UE that supports or is otherwise configured fortransmissions, such as periodic transmissions, of relatively small datapackets. For example, the UE 115-a may include a URLLC UE that supportsoperations and data communication associated with factory automation(e.g., automated manufacturing, supply chain management), transport(e.g., vehicle-to-vehicle (V2V) communications,vehicle-to-infrastructure (V2I) communications), or electrical powerdistribution (e.g., power grid networking) within a supported area orlocale, among other possible implementations.

Additionally or alternatively, the UE 115-b may support eMBBtransmissions associated with high data rates across wide coverage areas(such as geographic coverage area 110-a) supported by the base station105-a. In some examples, compared to URLLC communications, eMBBcommunications may be associated with relatively relaxed (e.g., longer)latency targets or thresholds, lower reliability targets or thresholds,or both. Moreover, one or more of UE 115-a and UE 115-b may support datacommunications associated with multiple service deployments (such asURLLC and eMBB), as part of an intra-UE or inter-UE operation.

To support the conditions associated with the URLLC and eMBB servicedeployments, or other types of resource allocation based oncommunication prioritization, the base station 105-a and the UEs 115-aand 115-b may support various techniques for dynamic uplink resourceallocations and uplink transmission cancellation or preemption. Forexample, the base station 105-a may be configured to transmit a ULCIbased at least in part on determining a reallocation of uplink resources(e.g., associated with uplink resources allocated to one or both of theUE 115-a or 115-b), and the UEs 115-a and 115-b may monitor for suchULCIs to determine how they should proceed with uplink communications.In other words, the UEs 115 may be notified about canceled uplinkresources in the time domain and frequency domain. In various examples,each of the UE 115-a or the UE 115-b may perform uplink communicationdeterminations such as determining whether to perform or proceed withuplink transmissions using at least a portion of theirpreviously-allocated uplink resources, or determining to refrain fromusing at least a portion of their previously-allocated uplink resources,or determining to await another allocation of uplink resources beforeinitiating or resuming uplink communications, or other determinations.

ULCIs may be signaled by the base station 105-a to UEs 115 (e.g., one orboth of the UEs 115-a or 115-b, a group of UEs) according to varioustechniques. For example, a UE 115 may be configured to monitor for ULCIsaccording to various signaling by the base station 105-a, such asvarious types of downlink control signaling, physical channel signaling,cell-specific signaling, and others. In some examples, ULCIs may beconveyed in downlink control information (DCI) over a physical downlinkcontrol channel (PDCCH), which may support UE-specific ULCIs. In someexamples, a UE 115 may be configured (e.g., by the base station 105-a)with a radio network temporary identifier (RNTI) for monitoring a PDCCHthat may be carrying ULCIs. In various examples, a UE 115 may beconfigured with an RNTI that is common between uplink and downlinkcancellation or preemption indications, or different between uplink anddownlink cancellation or preemption indications.

In some examples, ULCIs may be configured or conveyed in a group-commonphysical downlink control channel (GC-PDCCH) or otherwise conveyed ingroup-common DCI (GC-DCI), or DCI format 2_1, which may supportsignaling ULCIs that are relevant to sets of one or more UEs 115, andmay reduce signaling overhead as compared to ULCIs that are conveyed inUE-specific signaling. In some examples, ULCIs, or GC-PDCCH or GC-DCIindications, may be configured for UEs 115 configured for particularcommunications, such as eMBB communications (e.g., configured for eMBBUEs).

In some examples, uplink cancellation may include various configurationsby way of RRC configuration or other connection establishment betweenthe base station 105-a and UEs 115. For example, such configurations maybe signaled to UEs 115 (e.g., by the base station 105-a) in aninformation element (IE) or other configuration for uplink cancellation(e.g., an UplinkCancellation or UplinkPreemption IE, an int-RNTIconfiguration).

ULCIs may also be configured to be associated with a particularbandwidth in the frequency domain (e.g., a frequency carrier, afrequency channel, a bandwidth part, a set of one or more physicalresource blocks (PRBs) in the frequency domain). In one example, UEs 115may be configured according to uplink bandwidth parts, and a set of PRBsfor a received ULCI may be equal to or otherwise correspond to an activeuplink bandwidth part configured for the UE 115. In such examples,cancellation or preemption associated with ULCIs may correspond to anentire configured uplink bandwidth or uplink bandwidth part (e.g.,uplink preemption without frequency-domain partitioning), orcancellation or preemption associated with ULCIs may correspond tocertain portions of resources of a configured uplink bandwidth or uplinkbandwidth part (e.g., uplink preemption with frequency-domainpartitioning). Such divisions or partitioning may be referred to as agranularity of resources in the frequency domain for uplinkcancellation.

ULCIs may also be configured to be associated with particularcommunication resources in the time domain, which may be configured byRRC configuration (e.g., by the base station 105-a) or otherconfiguration. For example, resources in the time domain for whichcancellation is applied (e.g., corresponding to a ULCI) may be indicatedin symbol-level intervals (e.g., symbol durations, OFDM symboldurations), such as sets of 7-symbol durations or sets of 14-symboldurations, or may be indicated in sub-slots, such as 7 sub-slots eachhaving a length of two symbol durations or four symbol durations. Suchdivisions or partitioning may be referred to as a granularity ofresources in the time domain for cancellation, and, in some examples,such a granularity of resources in the time domain may be common betweenuplink cancellation or preemption and downlink cancellation orpreemption.

In various examples, a granularity of time domain resources for uplinkcancellation may depend on the granularity of frequency domainpartitioning, or the granularity of resources in the time domain and thefrequency domain may be otherwise interrelated. For example, for a givennumber of bits in a cancellation bitfield, when granularity of frequencydomain partitioning is relatively finer, granularity of time domainpartitioning may be relatively coarser. In one illustrative example, afirst configuration may include time domain partitioning at a symbollevel with no frequency domain partitioning, and a second configurationmay include time domain partitioning at a subslot level with frequencydomain partitioning (e.g., according to two divisions in the frequencydomain). In various examples, cancellation may be indicated, for subsetsof resources corresponding to a given ULCI, by bits of a bitfieldincluded in the ULCI, which may be associated with more-flexible uplinkcancellation, such as relatively greater options for resource puncturingpatterns or relatively flexible quantities of canceled symbols thanother techniques.

In some examples, the wireless communications system 200 may supportmore than one pattern of resources in ULCIs, such as supporting ULCIswith or without frequency-domain partitioning. The base station 105-a orother network entity may determine one of the patterns of resources forULCIs, and signal a configuration to UEs 115 (e.g., via downlink controlsignaling, via RRC configuration) so the UEs 115 can properly interpretULCIs received from the base station 105-a (e.g., according to thedetermined pattern). In one example, a UE 115 may support interpretingULCIs (e.g., bitfields of a ULCI) according to two patterns ofcommunication resources, and may be configured (e.g., by the basestation 105-a) for one of the two patterns based on the value of abitfield in a configuration register or DCI (e.g., a variable or IEtimeFrequencySet). In an illustrative example, when the value of thebitfield is 0, the ULCI may be configured for or interpreted accordingto time-domain partitioning at a symbol level and without frequencydomain partitioning, and when the value of the bitfield is 1, the ULCImay be configured for or interpreted according to time-domainpartitioning at a sub-slot level and with frequency domain partitioning(e.g., dividing an active uplink bandwidth part into two subbands forthe purpose of uplink cancellation).

In some examples, ULCIs may be configured for, or include an indicationof various repetition techniques. For example, DCI corresponding toULCIs may include a number of bits (e.g., 1 or 2 bits, a first two bitsof a ULCI bitfield) indicating a number of repetitions corresponding toa particular ULCI (e.g., from the time it decodes a ULCI). In anillustrative example, for a two-bit repetition indication, a value of 00may indicate 0 repetitions, a value of 01 may indicate one repetition, avalue of 10 may indicate two repetitions, and a value of 11 may indicatethree repetitions. In various examples repetition may be applied at abit level or a string level. In other examples, a UE 115 may bemore-generally configured to interpret or apply repetition to receivedULCIs, which may reduce signaling overhead associated with repetitionindications.

In an illustrative example, a UE 115 may be configured to identify ormap a ULCI bitfield in group-common DCI (GC-DCI) as 100000111, andinterpret the first two bits (e.g., 10) as a repetition indication thatindicates two repetitions (e.g., assuming the UE 115 is configured with7-bit ULCIs at a symbol level). Accordingly, the UE may apply thecancellation pattern indicated by the remaining bits (e.g., 0000111, abitfield having a length of 7 bits) three times. When the UE isconfigured to apply bit-level repetition, the UE may interpret thepattern indicated by the ULCI bitfield as |000|000|000|000|111|111|111|,where the vertical bars are added for illustrative clarity to show thateach bit is repeated three times before moving to the next remaining bitin the bitfield. When the UE is configured to apply string-levelrepetition, the UE may interpret the pattern indicated by the ULCIbitfield as |0000111|0000111|0000111|, where the vertical bars are addedfor illustrative clarity to show that the entire string of remainingbits is interpreted before the string of remaining bits is repeatedagain (e.g., according to the indicated two repetitions). Thus, ineither case, the indicated repetition may support a UE identifying 21resources of the ULCI that may or may not be subject to cancellationbased on 7 bits of a bitfield. In various cases, the above scenarios mayassume no frequency domain partitioning, or may include frequency domainpartitioning. These and other techniques for indicating repetitions ofuplink cancellation may be combined with configurations for granularityin the time domain and frequency domain (e.g., a particular set ofresources corresponding to each of the bits in the bitstring), and otheraspects of ULCIs.

In another example, the wireless communications system 200 may support aconfiguration or preconfiguration (e.g., at the base station 105, at theUEs 115) with a set of patterns for cancellation, including staticconfigurations, semi-static configurations, configuration by a networkentity (e.g., of a core network 130), and others. In such examples, thebase station 105-a may select one of the configured set of patterns, andtransmit an indication to UEs 115 identifying the selected pattern. UEs115 may receive the indication, and accordingly process received ULCIsaccording to the indicated pattern when interpreting a received ULCI(e.g., to support determining whether the received ULCI applies to anallocation of uplink resources). In various examples, suchconfigurations or preconfigurations may be specific to particular UEs115, may be common to sets of UEs 115 (e.g., according to group-commonsignaling, according to UEs configured for a type of communications), ormay be common to all UEs 115 served by a cell or base station 105.

In some examples, patterns may be defined according to a start andlength indicator value (SLIV), or a SLIV table, which may refer to astarting symbol or other time for uplink cancellation and a length orduration for cancellation. In various examples, the number of rows ofsuch a table may correspond to or otherwise be associated with a numberof bits for signaling a particular row. For example, for a SLIV tablewith 16 rows, a SLIV indication signaling may be associated with 4 bits.In various examples, signaling of a such a cancellation resource pattern(e.g., a row of a SLIV table) may accompany a ULCI, or such signalingmay precede a ULCI and the ULCI itself may signal when the indicatedpattern should be considered or applied for cancellation (e.g., in asingle bit or flag). In an illustrative example, the base station 105-amay configure a SLIV table for one or more UEs 115 (e.g., an eMBB UE, aUE configured for eMBB communications) that defines a set of SLIVpatterns for cancellation, and a bitwidth of the ULCI may be determinedbased on this SLIV table. In some cases, signaling that indicates whichof a set of preconfigured cancellation patterns should be applied inuplink cancellation may be associated with lower signaling overhead thanother techniques, such as signaling an entire bitfield for acancellation pattern with each ULCI.

FIGS. 3A and 3B illustrate examples for mapping a bitfield of a ULCI tocommunication resources for uplink transmission cancellation inaccordance with the present disclosure. For example, each of the mapping300-a and the mapping 300-b illustrate examples for how a bitfield witha value of 00011111010000 (e.g., a bitmap having a length of 14 bits)may be mapped to resources in the time and frequency domain for uplinkcancellation, where a value of ‘0’ indicates that cancellation is notapplied or enabled for the indicated resources (e.g., a frequency-timepart), and a value of ‘1’ indicates that cancellation is applied orenabled for the indicated resources. In other words, each of the mapping300-a and the mapping 300-b illustrate examples of dividing time andfrequency resources into 14 parts, mapped with 14 bits for uplinkcancellation indications.

The mapping 300-a illustrates an example where frequency domainpartitioning is not used or configured in a ULCI. For example, thebitfield may correspond to a duration 310-a in the time domain and abandwidth 315-a in the frequency domain, where the duration 310-a may beequal to the cancellation indication periodicity. In some examples, thebandwidth 315-a may correspond to a configured uplink bandwidth part(e.g., for a UE 115, for a set of UEs 115). In one illustrative example,the bandwidth 315-a may be 10 MHz, but the described techniques mayapply to other bandwidths 315-a. The mapping 300-a may be appliedaccording to a start time 330-a, which, in some examples, may bemeasured or initiated based at least in part on a time that a particularULCI is received (e.g., a ULCI symbol, a ULCI symbol duration) and aconfigured time offset. When the cancellation indication periodicity forthe mapping 300-a is 2 slots (e.g., 28 symbols), each bit in thebitfield may correspond to a duration 320-a in the time domain equal totwo symbols (e.g., two symbol durations). Thus, each bit may correspondto a subset of the communication resources corresponding to the mapping300-a, where the subset refers to a single instance of communicationresources having the duration 320-a and the bandwidth 315-a, following asequential order in the time domain. When a bit in the bitfield has avalue of 1, cancellation may apply across the entire bandwidth 315-a(e.g., across an entire configured uplink bandwidth part).

The mapping 300-b illustrates an example where frequency domainpartitioning is used or configured in a ULCI. For example, the bitfieldmay correspond to a duration 310-b in the time domain and a bandwidth315-b in the frequency domain, where the duration 310-b may be equal tothe cancellation indication periodicity. In various examples, theduration 310-b and the bandwidth 315-b of the mapping 300-b may or maynot be equal to the duration 310-a and the bandwidth 315-a of themapping 300-a. For example, the bandwidth 315-b may also correspond to aconfigured uplink bandwidth part (e.g., for a UE 115, for a set of UEs115). In one illustrative example, the bandwidth 315-b may also be 10MHz, but the described techniques may apply to other bandwidths 315-b.The mapping 300-b may be applied according to a start time 330-b, whichmay also be measured or initiated based at least in part on a time thata particular ULCI is received and a configured time offset.

When the cancellation indication periodicity for the mapping 300-b is 2slots (e.g., 28 symbols), each bit in the bitfield may correspond to aduration 320-b in the time domain of four symbols (e.g., four symboldurations). However, in the example of mapping 300-b, each bit in thebitfield may correspond to a fraction of the bandwidth 315-b, equal tothe bandwidth 325-b. In other words, each bit may correspond to a subsetof the communication resources corresponding to the mapping 300-b, wherethe subset refers to a single instance of communication resources havingthe duration 320-b and the bandwidth 325-b, following an order in asawtooth pattern as shown. In other words, a first bit in a pair of bitsfor a symbol group may be applicable to a lower subset of the bandwidth315-b (e.g., a lower subset of an active uplink bandwidth part) and asecond bit in the pair of bits for a symbol group may be applicable toan upper subset of the bandwidth 315-b (e.g., an upper bandwidth 325-b,an upper subset of an active uplink bandwidth part). However, otherpatterns for interpreting a bitfield across the mapping 300-b may beused.

In some examples, a wireless communication system may support uplinkcancellation according to either the mapping 300-a or the mapping 300-b.Thus, a base station 105 may select either the mapping 300-a or themapping 300-b, and generate ULCIs accordingly. For UEs 115 to interpretthe ULCIs correctly (e.g., so that UEs 115 and the base station 105 havethe same understanding of time and frequency uplink resources that arebeing canceled), the base station 105 may signal which of the twomappings has been configured for ULCIs, which may refer to an indicationof the granularity for time-frequency resources for uplink cancellation.In some examples, such an indication may be configured in DCI accordingto a value of a variable timeFrequencySet that is associated with uplinkcancellation granularity. If the base station 105 has selected themapping 300-a, the base station 105 may set the value oftimeFrequencySet to 0, and if the base station 105 has selected themapping 300-b, the base station 105 may set the value oftimeFrequencySet to 1. In some examples, a wireless communication systemmay support uplink cancellation according to both the mapping 300-a andthe mapping 300-b simultaneously, and may signal the configuration forrespective subsets of ULCIs or UEs 115 configured to monitor respectivesubsets of ULCIs (e.g., according to monitoring resource sets, accordingto configured bandwidth parts).

FIGS. 4A and 4B illustrate examples of processing timelines 400-a and400-b that support uplink transmission cancellation in accordance withaspects of the present disclosure. The processing timelines 400-a and400-b may illustrate aspects of communications performed by a wirelesscommunications system 100 or 200, and may illustrate an example ofapplying the mapping 300-a, described with reference to FIG. 3A, foruplink cancellation, where the mapping 300-a is applied withsymbol-level granularity in the time domain. The processing timelines400-a and 400-b may illustrate a sequence of symbol durations 410, butthe described techniques are also applicable to other durations.Further, although described in the context of the mapping 300-a, thedescribed techniques may be applicable to other mapping, such as mapping300-b, or other configured mapping such as a SLIV.

The processing timeline 400-a may begin with a ULCI symbol 420-a,indicative of a symbol or symbol duration in which a ULCI is received ata UE 115. In some examples, the ULCI symbol 420-a may be a last symbolof a CORESET where a UE 115 is configured to monitor PDCCH or GC-PDCCHfor ULCIs. Like the mapping 300-a described with reference to FIG. 3A,the ULCI associated with the ULCI symbol 420-a may include a bitfieldhaving a value of 0001111101000, where a value of 0 indicates thatuplink cancellation is not applied for the indicated resources, and avalue of 1 indicates that uplink cancellation is applied for theindicated resources.

The particular resources for which uplink cancellation is indicated bythe bitfield may be based at least in part on a time at which a ULCI isreceived (e.g., the ULCI symbol 420-a, an uplink cancellationindication), and a time required to process and respond or react to thereceived ULCI. In the example of processing timeline 400-a, a referencetime 425-a may be aligned in time with the end of the ULCI symbol 420-a.A time offset X may be applied or added to the reference time 425-a toidentify a time 430-a, where the time offset X may be associated with anaction time, a round trip time (RTT), a processing time, or other offsetbetween receiving a ULCI and various processing operations. In somecases, the offset X may be UE-specific, or based on a UE capability. Insome examples, the offset X may correspond to or be otherwise based on atime N₂, which may refer to a physical uplink shared channel (PUSCH)preparation time. For example, the UE processing time for ULCIs may beequal to, or shorter than the time N₂, or some other reference,preparation, or processing time (e.g., a PUSCH cancelation time). In theexample of processing timeline 400-a, the time offset X may have aduration of 4.5 symbols. In other examples, the time offset X may have aduration of 5.5 symbols, or some other duration.

A base station 105 or a UE 115 may identify resources for uplinkcancellation based on the time 430-a according to various techniques. Inthe example of processing timeline 400-a, the bitfield may be mapped toa first symbol following the time 430-a (e.g., a symbol starting at time440-a), and across a set of symbols 450-a. In other words, in theexample of processing timeline 400-a, the start time 330-a of themapping 300-a may be aligned with the time 440-a of the processingtimeline 400-a, and the duration 310-a of the mapping 300-a maycorrespond to the set of symbols 450-a. Thus, in the example ofprocessing timeline 400-a, there may be five symbol durations 410-abetween the end of the ULCI symbol 420-a and the start of uplinkcancellation (e.g., time 440-a) corresponding to the ULCI symbol 420-a.In some examples, a UE 115 may refrain from transmitting on those uplinkresources indicated to be canceled or preempted by the processingtimeline 400-a (e.g., symbol durations having a value of “1”). In someexamples, a cancellation determination by a UE 115 may be based onadditional considerations, including those described with reference tothe wireless communications system 500 described with reference to FIG.5.

The processing timeline 400-b may illustrate another example for mappingindications of a ULCI to communications resources, where the mapping isbased on an uplink/downlink TDD configuration, which may refer to asemi-static configuration between a base station 105 and a UE 115 (e.g.,as indicated by a setting of TDD-UL-DL-ConfigurationCommon). Certainsymbols of the processing timeline 400-b are indicated according to anexample uplink/downlink TDD configuration, where “U” represents anuplink symbol, “D” represents a downlink symbol, and “X” represents aflexible symbol that may be dynamically configured as uplink ordownlink.

The processing timeline 400-b may begin with a ULCI symbol 420-b,indicative of a symbol or symbol duration in which a ULCI is received ata UE 115, which may share characteristics of the ULCI symbol 420-adescribed with reference to FIG. 4A. In the example of processingtimeline 400-b, a reference time 425-b may be aligned in time with theend of the ULCI symbol 420-b. A time offset X may be applied or added tothe reference time 425-b to identify a time 430-b. In the example ofprocessing timeline 400-b, the bitfield may be mapped to a first symbolconfigured for uplink (e.g., indicated with a “U”) following the time430-b (e.g., a symbol starting at time 440-b), and may span across a setof symbols 450-b. In other words, in the example of processing timeline400-b, the start time 330-a of the mapping 300-a may be aligned with thetime 440-b of the processing timeline 400-b, and the duration 310-a ofthe mapping 300-a may correspond to the set of symbols 450-b. Thus, inthe example of processing timeline 400-b, there may be seven symboldurations 410-b between the end of the ULCI symbol 420-b and the startof uplink cancellation (e.g., time 440-b) corresponding to the ULCIsymbol 420-b. However, such a set of durations may change depending on aparticular TDD configuration of the base station 105 or the UE 115.Although the bitfield mapping of the processing timeline 400-b isdescribed in the context of a first symbol configured for uplinkfollowing the time 430-b, in other examples, a bitfield may be mappedaccording to a first uplink or special symbol following the time 430-b(e.g., whichever comes sooner). In some examples, a UE 115 may refrainfrom transmitting on those uplink resources indicated to be canceled orpreempted by the processing timeline 400-b (e.g., symbol durationshaving a value of “1”). In some examples, a cancellation determinationby a UE 115 may be based on additional considerations, including thosedescribed with reference to the wireless communications system 500described with reference to FIG. 5.

Although the processing timeline 400-b illustrates an example where,from a time 440, a bitfield is mapped to each of a set of consecutivesymbol durations 410, other examples of a processing timeline 400 maynot be mapped to consecutive symbol durations 410. In other words, themapping of a bitfield for other processing timelines 400 (not shown) mayhave gaps according to certain techniques. For example, because a UE 115may not expect that a ULCI bitmap would indicate uplink cancellation onsymbols configured for downlink communications (e.g., according to asemi-static configuration, as indicated byTDD-UL-DL-ConfigurationCommon), the UE 115 may interpret the bitfield ofa ULCI to instead be mapped only to those symbol durations that areconfigured as uplink symbol durations, or mapped only to those symboldurations that are configured as uplink or flexible symbol durations(e.g., skipping over those symbol durations that are configured asdownlink symbol durations). Such techniques may reduce signalingoverhead, since bits of a ULCI may not be wasted on indications forresources allocated to downlink transmissions.

FIG. 5 illustrates an example of a wireless communications system 500and corresponding operations that support uplink transmissioncancellation in accordance with aspects of the present disclosure. Insome examples, the wireless communications system 500 may implementaspects of wireless communications systems 100 or 200 described withreference to FIGS. 1 and 2. The wireless communications system 500includes a base station 105-c and a UE 115-c, which may be examples ofbase stations 105 and UEs 115 described herein.

At 510, the base station 105-c may signal an allocation of uplinkresources, which may be received by the UE 115-c

At 520, the base station 105-c may determine a reallocation ofresources. In some examples, the reallocation at 520 may be related tosupporting a particular type or category of communications, orsupporting particular UEs 115 configured for a particular type orcategory of communications (e.g., URLLC communications, URLLC UEs). Insome examples, determining the reallocation may be based at least inpart on a configured time offset, such as a processing time offset,which may be based at least in part on a capability of the UE 115-c.

At 530, the base station 105-c may signal a ULCI, which may be receivedby the UE 115-c. In various examples, the ULCI may be UE-specific, orcommon to a set of one or more UEs 115. For example, the ULCI may besignaled using a GC-PDCCH transmission or other DCI or GC-DCI.

At 540, the UE 115-c may determine whether the allocation of resources(e.g., as signaled at 510) is canceled. For example, the UE 115-c mayidentify a bitmap of the ULCI associated with a set of communicationresources in the time domain and frequency domain, and determine whetherat least a portion of the allocation of uplink resources corresponds toone or more of the subsets of the communication resources for whichcancellation applies. In various examples, determining whether theallocation of uplink resources is canceled may be based at least in parton a type of physical channel associated with uplink communications, atype of physical channel associated with the uplink cancellationindication, an allocation type associated with the identified allocationof uplink resources, a type or priority of communications associatedwith the ULCI, or a type or priority of subsequent uplinkcommunications.

In some examples, ULCIs may have various dependence on or relationshipswith dynamic grants, such as uplink grants received over DCI, includingthe relationships and scenarios described herein. In other words, insome examples, determinations of uplink cancellation at 540 may be basedat least in part on various scenarios for dynamic grants (e.g., based atleast in part on a dynamic or DCI allocation category or type).

In one example, a later DCI scheduling of an uplink transmission (e.g.,for URLLC communications, for higher-priority communications) mayoverwrite the cancellation of the ULCI received at 530. In other words,the UE 115-c may receive the ULCI at 530, but may also receive a dynamicuplink grant (e.g., for resources corresponding to or otherwiseindicated by the ULCI) that causes the UE 115-c to ignore the ULCI of530. For example, when the ULCI of 530 indicates that symbols 10-13 in aslot are canceled or preempted (e.g., for URLLC transmission), the UE115-c may receive a DCI scheduling of URLLC PUSCH on symbols 12-13, andaccordingly transmit an uplink transmission (e.g., a PUSCH transmission)on symbols 12-13. Thus, despite resources being indicated as canceled orpreempted by the ULCI received at 530, the UE 115-c may still transmitan uplink transmission on those resources, such that the UE 115-ceffectively ignores the ULCI of 530. In some examples, the ULCI 530 maybe configured (e.g., by the base station 105-c) to clear lower-prioritytransmissions, at least in part to support the URLLC PUSCH transmissionof the UE 115-c (e.g., on symbols 12-13).

In another example, the UE 115-c may not expect to receive a DCI grantallocating resources for uplink transmission for eMBB within symbolsindicated to be canceled or preempted by ULCI. Rather, because the UE115-c recognizes the ULCI of 530 as preempting eMBB communications(e.g., based on a type of communications corresponding to the ULCI), theUE 115-c may ignore such a subsequent DCI grant for eMBB communications(e.g., as an error condition). In other words, when the UE 115-c decodesa ULCI corresponding to a particular type or priority of communications,the UE 115-c may ignore subsequent uplink grants associated with thesame particular type or priority of communications that would conflictwith resources canceled or preempted by the ULCI of 530.

In another example, the UE 115-c may not expect to receive, in the samemonitoring occasion, an uplink grant for eMBB transmission and an ULCIthat would puncture or otherwise cancel or preempt the eMBBtransmission. Rather, because the base station 105-c should not schedulethe UE 115-c for communications that would need to be separatelypunctured or preempted by the ULCI of 530, the UE 115-c may ignore sucha grant for eMBB transmission (e.g., as an error condition). In otherwords, when the UE 115-c decodes a ULCI that would puncture allocatedcommunications (e.g., of a same communications type or category) in thesame monitoring occasion, the UE 115-c may ignore the uplink grants thatwould be punctured by the ULCI of 530.

In another example, the UE 115-c may receive, in the same monitoringoccasion, an uplink grant (e.g., a DCI grant) for URLLC transmission andan ULCI for eMBB cancellation. In this case, the UE 115-c will ignorethe ULCI for those resources that URLLC DCI grants. In other words, moregenerally, when the UE 115-c decodes a ULCI of 530 that is associatedwith lower-priority communications than an uplink grant or otherallocation of uplink resources, the UE 115-c may ignore the at least aportion of the ULCI of 530. In such examples, the ULCI 530 may beconfigured (e.g., by the base station 105-c) to clear lower-prioritytransmissions, at least in part to support the uplink grant for URLLCtransmission of the UE 115-c.

In some examples, eMBB grants may be allowed to overwrite a ULCI of 530.For example, the UE 115-c may be configured to ignore a ULCI of 530 whenthe UE 115-c is configured to transmit a physical uplink control channel(PUCCH) carrying acknowledgement signaling (e.g., ACK/NACK for eMBBcommunications), or configured to transmit a PRACH that is triggered byPDCCH (e.g., PDCCH-ordered PRACH transmission).

In some examples, the base station 105-c or the UE 115-c may interpretor evaluate uplink cancellation of random access transmissions (e.g.,PRACH transmissions) according to various conditions related to randomaccess signaling or requests, or conditions associated with a connectionwith the base station 105-c (e.g., based on conditions for which a PRACHtransmission is triggered). For example, various events may triggerPRACH transmissions by the UE 115-c, such as an initial access followingan idle state (e.g., according to RRC IDLE), a connectionreestablishment (e.g., according to an RRC connection re-establishmentprocedure), data arrival during a connected state when the UE 115-c andthe base station 105-c are not synchronized (e.g., downlink or uplinkdata arrival during an RRC_CONNECTED state when an uplinksynchronization status is “non-synchronised”), data arrival during aconnected state when resources for scheduling requests are unavailable(e.g., uplink data arrival during an RRC_CONNECTED state when there areno PUCCH resources available for scheduling requests), schedulingrequest failures, handover requests (e.g., a request by a radio resourcecontroller upon synchronous reconfiguration), a transition from aninactive state (e.g., an RRC_INACTIVE state), to establish timealignment for an addition of a secondary cell, beam failure recovery, arequest for other system information, or various other conditions.

Depending on how the random access transmissions for the UE 115-c aretriggered, the UE 115-c may or may not be able to apply, or be expectedto apply cancellation or preemption indications of a ULCI of 530. Forexample, during an initial access (e.g., from an idle state, uponconnection establishment), the identity of the UE 115-c may not be knownto the base station 105-c, and thus the base station 105-c may not haveenough information to preempt or cancel PRACH transmissions by the UE115-c. In another example, a downlink connection from the base station105-c to the UE 115-c may be unreliable during a PRACH procedure, andaccordingly the UE 115-c may not be able to successfully receive ordecode a ULCI of 530. Accordingly, the base station 105-c may not beable to assume that PRACH transmissions of the UE 115-c would besuccessfully preempted or canceled (e.g., by a ULCI of 350). In otherexamples, such as events where PRACH transmissions are triggered by thebase station 105-c (e.g., due to an uplink connection with the UE 115-cbeing non-synchronized, when a downlink connection remains reliable,according to PDCCH-ordered PRACH), the base station 105-c may be able toassume that PRACH transmissions would be successfully preempted orcanceled. Thus, in some circumstances, the base station 105-a mayproceed with a reallocation of uplink resource at 520, and atransmission of a ULCI at 530, based on triggering conditions associatedwith random access transmissions (e.g., PRACH transmissions).

In another example related to random access transmission triggering, theUE 115-c may not expect to receive (e.g., in a same monitoring occasion)signaling to trigger a random access transmission by the UE 115-c (e.g.,a PDCCH-ordered PRACH) and a ULCI that would puncture or otherwisecancel or preempt the random access transmission. Rather, because thebase station 105-c should not schedule the UE 115-c for random accesstransmissions that would need to be separately punctured or canceled bythe ULCI of 530, the UE 115-c may ignore such a trigger for a randomaccess transmission (e.g., as an error condition). In other words, whenthe UE 115-c decodes a ULCI that would cancel a triggered random accesstransmission (e.g., in the same monitoring occasion), the UE 115-c mayignore the trigger for the random access transmission.

In some examples, the UE 115-c may be configured to monitor ULCI after(e.g., based at least in part on) being scheduled for dynamic eMBB PUSCHtransmission, or other transmissions that may be preempted by ULCIs.Additionally or alternatively, if the UE 115-c is not scheduled for eMBBtransmission (e.g., eMBB PUSCH) or other transmissions that may bepreempted by ULCIs, the UE 115-c may not need to monitor forcancellation, and accordingly may be configured to avoid or refrain fromsuch monitoring, which may reduce power consumption or processorutilization at the UE 115-c. In some examples, the UE 115-c may beconfigured to monitor for uplink cancellation of other transmissions,such as after being triggered for asynchronous SRS (A-SRS).

In some examples, ULCIs may have various dependence on or relationshipswith higher-layer configured transmissions or configured grants,including the relationships and scenarios described herein. In otherwords, in some examples, determinations of uplink cancellation at 540may be based at least in part on various scenarios for higher-layerconfigured transmissions (e.g., based at least in part on a higher-layerallocation category or type).

In one example, if the UE 115-c is configured by higher layers totransmit PUCCH, or PUSCH, or PRACH in the set of symbols of the slot,and the UE 115-c receives ULCI indicating that some of the resourceswithin the set of symbols (e.g., for eMBB transmission) are preempted,then the UE 115-c may not transmit the configured PUCCH, or the PUSCH,or the PRACH in the slot. In other words, in contrast with dynamicgrants received over DCI, in some examples, when a ULCI indicates acancellation of uplink resources corresponding to higher-layerconfigured transmissions or configured grants (e.g., corresponding toPUCCH, PUSCH, or PRACH transmissions), the UE 115-c may not beconfigured to ignore the ULCI of 530.

In another example, if the UE 115-c is configured by higher layers totransmit a sounding reference signal (SRS) in the set of symbols of theslot, and the UE 115-c receives the ULCI of 530 indicating that at leastsome of the set of symbols are being preempted, the UE 115-c maytransmit the SRS only in a subset of symbols from the set of symbols ofthe slot that are not being impacted by the ULCI (e.g., symbols that arenot indicated for cancellation). However, in such examples, such aconfiguration may not imply that the UE 115-c with higher layerconfigured transmission is required to monitor for ULCIs. For example,ULCI may have been monitored and received after the UE 115-c wasscheduled for dynamic PUSCH transmission (e.g., according to anallocation of uplink resources at 510).

In some examples, the UE 115-c may be configured to drop or not drophigher-layer configured transmissions, which may be a configurationspecific to certain types of physical channels.

Additionally or alternatively, the UE 115-c may be configured withmultiple configurations for ULCI targeted for different channels (e.g.,different physical channels). In other words, ULCIs such as thosereceived at 530 may be configured differently for different channels.For example, the UE 115-c may be configured according to differentmonitoring periodicity for higher-layer configuration as compared withULCI monitoring for dynamic uplink grants (e.g., dynamic grants forPUSCH). In one example, the UE 115-c may be configured for periodic SRStransmissions according to an SRS periodicity, and the UE 115-c may beconfigured for cancellation monitoring according to a periodicity thatmatches the SRS periodicity. In other examples, ULCIs may have differentmonitoring periodicities or resource granularities depending on a typeof channel, or type of communications, or other communicationconfiguration of characteristic. In another example, for some higherlayer configured transmissions (e.g., one or more of PUCCH or PRACHtransmissions), the UE 115-c may be configured to ignore ULCIs, andproceed with transmissions of the higher-layer configured transmissionswhether or not a ULCI was received at 530.

In some examples, at 550, the UE 115-c may perform uplink communicationsbased at least in part on the outcome of 540, including transmissionsaccording to the scenarios described above. For example, the UE 115-cmay transmit an uplink transmission on a subset of the allocation ofuplink resources based on the outcome of 540, or the UE 115-c mayrefrain from using at least a portion of the allocation of uplinkresources based on the outcome of 540. In some examples, the UE 115-cmay refrain from using the allocation of uplink resources entirely, andinstead may wait for another allocation of resources prior to performinguplink communications.

FIG. 6 shows a block diagram 600 of a device 605 that supports uplinktransmission cancellation in accordance with aspects of the presentdisclosure. The device 605 may be an example of aspects of a UE 115 asdescribed herein. The device 605 may include a receiver 610, acommunication manager 615, and a transmitter 620. The device 605 mayalso include a processor. Each of these components may be incommunication with one another (e.g., via one or more buses).

The receiver 610 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to uplinktransmission cancellation, etc.). Information may be passed on to othercomponents of the device 605. The receiver 610 may be an example ofaspects of the transceiver 915 described with reference to FIG. 9. Thereceiver 610 may utilize a single antenna or a set of antennas.

The communication manager 615 may identify an allocation of uplinkresources associated with a first type of communications with a firstlatency threshold, receive an uplink cancellation indication associatedwith a second type of communications with a second latency thresholdthat is different from the first latency threshold, determine whetherthe identified allocation of uplink resources is canceled based on theuplink cancellation indication, and perform uplink communications ofeither the first type of communications or the second type ofcommunications based on the determining. The communication manager 615may be an example of aspects of the communication manager 910 describedherein.

The communication manager 615, or its sub-components, may be implementedin hardware, software (e.g., executed by a processor), or anycombination thereof. If implemented in code executed by a processor, thefunctions of the communication manager 615, or its sub-components may beexecuted by a general-purpose processor, a digital signal processor(DSP), an application-specific integrated circuit (ASIC), afield-programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described in thepresent disclosure.

The communication manager 615, or its sub-components, may be physicallylocated at various positions, including being distributed such thatportions of functions are implemented at different physical locations byone or more physical components. In some examples, the communicationmanager 615, or its sub-components, may be a separate and distinctcomponent in accordance with various aspects of the present disclosure.In some examples, the communication manager 615, or its sub-components,may be combined with one or more other hardware components, includingbut not limited to an input/output (I/O) component, a transceiver, anetwork server, another computing device, one or more other componentsdescribed in the present disclosure, or a combination thereof inaccordance with various aspects of the present disclosure.

The transmitter 620 may transmit signals generated by other componentsof the device 605. In some examples, the transmitter 620 may becollocated with a receiver 610 in a transceiver module. For example, thetransmitter 620 may be an example of aspects of the transceiver 915described with reference to FIG. 9. The transmitter 620 may utilize asingle antenna or a set of antennas.

FIG. 7 shows a block diagram 700 of a device 705 that supports uplinktransmission cancellation in accordance with aspects of the presentdisclosure. The device 705 may be an example of aspects of a device 605,or a UE 115 as described herein. The device 705 may include a receiver710, a communication manager 715, and a transmitter 735. The device 705may also include a processor. Each of these components may be incommunication with one another (e.g., via one or more buses).

The receiver 710 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to uplinktransmission cancellation, etc.). Information may be passed on to othercomponents of the device 705. The receiver 710 may be an example ofaspects of the transceiver 915 described with reference to FIG. 9. Thereceiver 710 may utilize a single antenna or a set of antennas.

The communication manager 715 may be an example of aspects of thecommunication manager 615 as described herein. The communication manager715 may include an uplink allocation manager 720, an uplink cancellationmanager 725, and an uplink communications manager 730. The communicationmanager 715 may be an example of aspects of the communication manager910 described herein.

The uplink allocation manager 720 may identify an allocation of uplinkresources associated with a first type of communications with a firstlatency threshold.

The uplink cancellation manager 725 may receive an uplink cancellationindication associated with a second type of communications with a secondlatency threshold that is different from the first latency threshold anddetermine whether the identified allocation of uplink resources iscanceled based on the uplink cancellation indication.

The uplink communications manager 730 may perform uplink communicationsof either the first type of communications or the second type ofcommunications based on the determining.

The transmitter 735 may transmit signals generated by other componentsof the device 705. In some examples, the transmitter 735 may becollocated with a receiver 710 in a transceiver module. For example, thetransmitter 735 may be an example of aspects of the transceiver 915described with reference to FIG. 9. The transmitter 735 may utilize asingle antenna or a set of antennas.

FIG. 8 shows a block diagram 800 of a communication manager 805 thatsupports uplink transmission cancellation in accordance with aspects ofthe present disclosure. The communication manager 805 may be an exampleof aspects of a communication manager 615, a communication manager 715,or a communication manager 910 described herein. The communicationmanager 805 may include an uplink allocation manager 810, an uplinkcancellation manager 815, an uplink communications manager 820, a bitmapinterpreter 825, and a cancellation timeline manager 830. Each of thesemodules may communicate, directly or indirectly, with one another (e.g.,via one or more buses).

The uplink allocation manager 810 may identify an allocation of uplinkresources associated with a first type of communications with a firstlatency threshold.

In some examples, the uplink allocation manager 810 may receive anuplink grant after receiving the uplink cancellation indication, theuplink grant including communication resources associated with theuplink cancellation indication.

The uplink cancellation manager 815 may receive an uplink cancellationindication associated with a second type of communications with a secondlatency threshold that is different from the first latency threshold.

In some examples, the uplink cancellation manager 815 may determinewhether the identified allocation of uplink resources is canceled basedon the uplink cancellation indication.

In some examples, the uplink cancellation manager 815 may determinewhether at least a portion of the allocation of uplink resourcescorresponds to one or more of the subsets of the communication resourcesfor which cancellation applies.

In some examples, the uplink cancellation manager 815 may determine thatthe respective subset of the communication resources corresponding toeach bit of the bitmap corresponds to uplink resources of anuplink/downlink time division duplex (TDD) configuration of the UE.

In some examples, the uplink cancellation manager 815 may receive acancellation configuration, prior to receiving the uplink cancellationindication, associated with a pattern of communication resources in thetime domain and frequency domain, where the uplink cancellationindication indicates a time for applying the pattern of communicationresources for cancellation.

In some examples, the uplink cancellation manager 815 may ignore atleast a portion of the uplink cancellation indication based on receivingthe uplink grant after receiving the uplink cancellation indication.

In some cases, the cancellation configuration includes a RRCconfiguration.

The uplink communications manager 820 may perform uplink communicationsof either the first type of communications or the second type ofcommunications based on the determining.

In some examples, the uplink communications manager 820 may transmit anuplink transmission on a subset of the allocation of uplink resourcesbased on the determining.

In some examples, the uplink communications manager 820 may refrain fromusing at least a portion of the allocation of uplink resources based onthe determining.

In some cases, the first type of communications includes enhanced mobilebroadband (eMBB) communications and the second type of communicationsincludes ultra-reliable low latency communications (URLLC).

The bitmap interpreter 825 may identify a bitmap of the uplinkcancellation indication associated with a set of communication resourcesin the time domain and frequency domain, each bit of the bitmapcorresponding to a respective subset of the communication resources, andeach bit indicating whether or not cancellation applies to therespective subset of the communication resources.

In some examples, the bitmap interpreter 825 may determine that thebitmap corresponds to an uplink bandwidth part configured for the UE.

In some examples, the bitmap interpreter 825 may identify a repetitionindicator.

In some examples, the bitmap interpreter 825 may repeat bits of thebitmap according to the repetition indicator, each repeated bit of thebitmap corresponding to a respective subset of the communicationresources, and each repeated bit indicating whether or not cancellationapplies to the respective subset of the communication resources.

The cancellation timeline manager 830 may determine a time for applyingcancellation based on a time of receiving the uplink cancellationindication and a configured time offset for cancellation.

FIG. 9 shows a diagram of a system 900 including a device 905 thatsupports uplink transmission cancellation in accordance with aspects ofthe present disclosure. The device 905 may be an example of or includethe components of device 605, device 705, or a UE 115 as describedherein. The device 905 may include components for bi-directional voiceand data communications including components for transmitting andreceiving communications, including a communication manager 910, atransceiver 915, an antenna 920, memory 925, and a processor 935. Thesecomponents may be in electronic communication via one or more buses(e.g., bus 940).

The communication manager 910 may identify an allocation of uplinkresources associated with a first type of communications with a firstlatency threshold, receive an uplink cancellation indication associatedwith a second type of communications with a second latency thresholdthat is different from the first latency threshold, determine whetherthe identified allocation of uplink resources is canceled based on theuplink cancellation indication, and perform uplink communications ofeither the first type of communications or the second type ofcommunications based on the determining.

The actions performed by the communication manager 910 as describedherein may be implemented to realize one or more potential advantages.One implementation may allow a UE 115 to be more-quickly allocated withuplink resources for higher priority communications, such as URLLCuplink transmissions, which may provide improved quality and reliabilityof service at the UE 115, as latency may be reduced

The transceiver 915 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described herein. For example, thetransceiver 915 may represent a wireless transceiver and may communicatebi-directionally with another wireless transceiver. The transceiver 915may also include a modem to modulate the packets and provide themodulated packets to the antennas for transmission, and to demodulatepackets received from the antennas.

In some cases, the wireless device may include a single antenna 920.However, in some cases, the device may have more than one antenna 920,which may be capable of concurrently transmitting or receiving multiplewireless transmissions.

The memory 925 may include random-access memory (RAM) and read-onlymemory (ROM). The memory 925 may store computer-readable,computer-executable code 930 including instructions that, when executed,cause the processor to perform various functions described herein. Insome cases, the memory 925 may contain, among other things, a basicinput output system (BIOS) which may control basic hardware or softwareoperation such as the interaction with peripheral components or devices.

The code 930 may include instructions to implement aspects of thepresent disclosure, including instructions to support wirelesscommunications. The code 930 may be stored in a non-transitorycomputer-readable medium such as system memory or other type of memory.In some cases, the code 930 may not be directly executable by theprocessor 935 but may cause a computer (e.g., when compiled,interpreted, converted, and/or executed) to perform functions describedherein.

The processor 935 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, anFPGA, a programmable logic device, a discrete gate or transistor logiccomponent, a discrete hardware component, or any combination thereof).In some cases, the processor 935 may be configured to operate a memoryarray using a memory controller. In other cases, a memory controller maybe integrated into the processor 935. The processor 935 may beconfigured to execute computer-readable instructions stored in a memory(e.g., the memory 925) to cause the device 905 to perform variousfunctions (e.g., functions or tasks supporting uplink transmissioncancellation).

FIG. 10 shows a block diagram 1000 of a device 1005 that supports uplinktransmission cancellation in accordance with aspects of the presentdisclosure. The device 1005 may be an example of aspects of a basestation 105 as described herein. The device 1005 may include a receiver1010, a communication manager 1015, and a transmitter 1020. The device1005 may also include a processor. Each of these components may be incommunication with one another (e.g., via one or more buses).

The receiver 1010 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to uplinktransmission cancellation, etc.). Information may be passed on to othercomponents of the device 1005. The receiver 1010 may be an example ofaspects of the transceiver 1320 described with reference to FIG. 13. Thereceiver 1010 may utilize a single antenna or a set of antennas.

The communication manager 1015 may transmit an allocation of uplinkresources associated with a first type of communications with a firstlatency threshold, determine a reallocation of the uplink resourcesbased on a second type of communications with a second latency thresholdthat is different from the first latency threshold, and transmit anuplink cancellation indication corresponding to the uplink resourcesbased on the determining. The communication manager 1015 may be anexample of aspects of the communication manager 1310 described herein.

The communication manager 1015, or its sub-components, may beimplemented in hardware, software (e.g., executed by a processor), orany combination thereof. If implemented in software executed by aprocessor, the functions of the communication manager 1015, or itssub-components may be executed by a general-purpose processor, a DSP, anapplication-specific integrated circuit (ASIC), a FPGA or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described in the present disclosure.

The communication manager 1015, or its sub-components, may be physicallylocated at various positions, including being distributed such thatportions of functions are implemented at different physical locations byone or more physical components. In some examples, the communicationmanager 1015, or its sub-components, may be a separate and distinctcomponent in accordance with various aspects of the present disclosure.In some examples, the communication manager 1015, or its sub-components,may be combined with one or more other hardware components, includingbut not limited to an input/output (I/O) component, a transceiver, anetwork server, another computing device, one or more other componentsdescribed in the present disclosure, or a combination thereof inaccordance with various aspects of the present disclosure.

The transmitter 1020 may transmit signals generated by other componentsof the device 1005. In some examples, the transmitter 1020 may becollocated with a receiver 1010 in a transceiver module. For example,the transmitter 1020 may be an example of aspects of the transceiver1320 described with reference to FIG. 13. The transmitter 1020 mayutilize a single antenna or a set of antennas.

FIG. 11 shows a block diagram 1100 of a device 1105 that supports uplinktransmission cancellation in accordance with aspects of the presentdisclosure. The device 1105 may be an example of aspects of a device1005, or a base station 105 as described herein. The device 1105 mayinclude a receiver 1110, a communication manager 1115, and a transmitter1135. The device 1105 may also include a processor. Each of thesecomponents may be in communication with one another (e.g., via one ormore buses).

The receiver 1110 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to uplinktransmission cancellation, etc.). Information may be passed on to othercomponents of the device 1105. The receiver 1110 may be an example ofaspects of the transceiver 1320 described with reference to FIG. 13. Thereceiver 1110 may utilize a single antenna or a set of antennas.

The communication manager 1115 may be an example of aspects of thecommunication manager 1015 as described herein. The communicationmanager 1115 may include an uplink allocation manager 1120, areallocation manager 1125, and a cancellation indication manager 1130.The communication manager 1115 may be an example of aspects of thecommunication manager 1310 described herein.

The uplink allocation manager 1120 may transmit an allocation of uplinkresources associated with a first type of communications with a firstlatency threshold.

The reallocation manager 1125 may determine a reallocation of the uplinkresources based on a second type of communications with a second latencythreshold that is different from the first latency threshold.

The cancellation indication manager 1130 may transmit an uplinkcancellation indication corresponding to the uplink resources based onthe determining.

The transmitter 1135 may transmit signals generated by other componentsof the device 1105. In some examples, the transmitter 1135 may becollocated with a receiver 1110 in a transceiver module. For example,the transmitter 1135 may be an example of aspects of the transceiver1320 described with reference to FIG. 13. The transmitter 1135 mayutilize a single antenna or a set of antennas.

FIG. 12 shows a block diagram 1200 of a communication manager 1205 thatsupports uplink transmission cancellation in accordance with aspects ofthe present disclosure. The communication manager 1205 may be an exampleof aspects of a communication manager 1015, a communication manager1115, or a communication manager 1310 described herein. Thecommunication manager 1205 may include an uplink allocation manager1210, a reallocation manager 1215, a cancellation indication manager1220, a bitmap generator 1225, a cancellation configuration manager1230, a cancellation timeline manager 1235, and an uplink communicationsmanager 1240. Each of these modules may communicate, directly orindirectly, with one another (e.g., via one or more buses).

The uplink allocation manager 1210 may transmit an allocation of uplinkresources associated with a first type of communications with a firstlatency threshold.

In some examples, the uplink allocation manager 1210 may transmit, to aUE, an uplink grant including communication resources associated withthe uplink cancellation indication, the uplink grant indicating to theUE to ignore at least a portion of the uplink cancellation indication.

The reallocation manager 1215 may determine a reallocation of the uplinkresources based on a second type of communications with a second latencythreshold that is different from the first latency threshold.

In some examples, the reallocation manager 1215 determine a reallocationof uplink resources allocated to a physical random access channel(PRACH) based at least in part on a triggering condition fortransmissions associated with the uplink resources allocated to thePRACH.

The cancellation indication manager 1220 may transmit an uplinkcancellation indication corresponding to the uplink resources based onthe determining.

In some examples, transmitting the uplink cancellation indicationincludes transmitting the bitmap.

In some examples, the cancellation indication manager 1220 may transmita repetition indicator associated with the bitmap.

In some examples, the cancellation indication manager 1220 may transmita group common physical downlink control channel (GC-PDCCH).

The bitmap generator 1225 may generate a bitmap associated with a set ofcommunication resources in the time domain and frequency domain, eachbit of the bitmap corresponding to a respective subset of thecommunication resources, and each bit indicating whether or notcancellation applies to the respective subset of the communicationresources.

The cancellation configuration manager 1230 may transmit a cancellationconfiguration, prior to transmitting the uplink cancellation indication,associated with a pattern of communication resources in the time domainand frequency domain, where the uplink cancellation indication indicatesa time for applying the pattern of communication resources forcancellation.

In some examples, the cancellation configuration manager 1230 maytransmit an RRC configuration.

The cancellation timeline manager 1235 may determine a time for applyingcancellation based on a time of transmitting the uplink cancellationindication and a configured time offset for cancellation.

The uplink communications manager 1240 may receive communications fromone or more user equipments (UEs) based on the reallocation of theuplink resources and transmitting the uplink cancellation indication.

In some cases, the first type of communications includes enhanced mobilebroadband (eMBB) communications and the second type of communicationsincludes ultra-reliable low latency communications (URLLC).

FIG. 13 shows a diagram of a system 1300 including a device 1305 thatsupports uplink transmission cancellation in accordance with aspects ofthe present disclosure. The device 1305 may be an example of or includethe components of device 1005, device 1105, or a base station 105 asdescribed herein. The device 1305 may include components forbi-directional voice and data communications including components fortransmitting and receiving communications, including a communicationmanager 1310, a network communications manager 1315, a transceiver 1320,an antenna 1325, memory 1330, a processor 1340, and an inter-stationcommunications manager 1345. These components may be in electroniccommunication via one or more buses (e.g., bus 1350).

The communication manager 1310 may transmit an allocation of uplinkresources associated with a first type of communications with a firstlatency threshold, determine a reallocation of the uplink resourcesbased on a second type of communications with a second latency thresholdthat is different from the first latency threshold, and transmit anuplink cancellation indication corresponding to the uplink resourcesbased on the determining.

The actions performed by the communications manager 1310 as describedherein may be implemented to realize one or more potential advantages.One implementation may allow a base station 105 or other network entityto more quickly reallocate uplink resources to different typescommunications, which may have different latency thresholds, reliabilitythresholds, or other prioritization. Another implementation may provideimproved quality and reliability of service for various UEs 115 of awireless communications system, as latency may be reduced andreliability may be improved for higher-priority communications.

The network communications manager 1315 may manage communications withthe core network (e.g., via one or more wired backhaul links). Forexample, the network communications manager 1315 may manage the transferof data communications for client devices, such as one or more UEs 115.

The transceiver 1320 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described herein. For example, thetransceiver 1320 may represent a wireless transceiver and maycommunicate bi-directionally with another wireless transceiver. Thetransceiver 1320 may also include a modem to modulate the packets andprovide the modulated packets to the antennas for transmission, and todemodulate packets received from the antennas.

In some cases, the wireless device may include a single antenna 1325.However, in some cases, the device may have more than one antenna 1325,which may be capable of concurrently transmitting or receiving multiplewireless transmissions.

The memory 1330 may include RAM and ROM. The memory 1330 may storecomputer-readable, computer-executable code 1330 including instructionsthat, when executed, cause the processor to perform various functionsdescribed herein. In some cases, the memory 1330 may contain, amongother things, a BIOS which may control basic hardware or softwareoperation such as the interaction with peripheral components or devices.

The code 1335 may include instructions to implement aspects of thepresent disclosure, including instructions to support wirelesscommunications. The code 1335 may be stored in a non-transitorycomputer-readable medium such as system memory or other type of memory.In some cases, the code 1335 may not be directly executable by theprocessor 1340 but may cause a computer (e.g., when compiled,interpreted, converted and/or executed) to perform functions describedherein.

The processor 1340 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, anFPGA, a programmable logic device, a discrete gate or transistor logiccomponent, a discrete hardware component, or any combination thereof).In some cases, the processor 1340 may be configured to operate a memoryarray using a memory controller. In other cases, a memory controller maybe integrated into the processor 1340. The processor 1340 may beconfigured to execute computer-readable instructions stored in a memory(e.g., the memory 1330) to cause the device 1305 to perform variousfunctions (e.g., functions or tasks supporting uplink transmissioncancellation).

The inter-station communications manager 1345 may manage communicationswith other base station 105, and may include a controller or schedulerfor controlling communications with UEs 115 in cooperation with otherbase stations 105. For example, the inter-station communications manager1345 may coordinate scheduling for transmissions to UEs 115 for variousinterference mitigation techniques such as beamforming or jointtransmission. In some examples, the inter-station communications manager1345 may provide an X2 interface within an LTE/LTE-A wirelesscommunication network technology to provide communication between basestations 105.

FIG. 14 shows a flowchart illustrating a method 1400 that supportsuplink transmission cancellation in accordance with aspects of thepresent disclosure. The operations of method 1400 may be implemented bya UE 115 or its components as described herein. For example, theoperations of method 1400 may be performed by a communication manager asdescribed with reference to FIGS. 6 through 9. In some examples, a UEmay execute a set of instructions to control the functional elements ofthe UE to perform the described functions. Additionally oralternatively, a UE may perform aspects of the described functions usingspecial-purpose hardware.

At 1405, the UE may identify an allocation of uplink resourcesassociated with a first type of communications with a first latencythreshold. The operations of 1405 may be performed according to themethods described herein. In some examples, aspects of the operations of1405 may be performed by an uplink allocation manager as described withreference to FIGS. 6 through 9.

At 1410, the UE may receive an uplink cancellation indication associatedwith a second type of communications with a second latency thresholdthat is different from the first latency threshold. The operations of1410 may be performed according to the methods described herein. In someexamples, aspects of the operations of 1410 may be performed by anuplink cancellation manager as described with reference to FIGS. 6through 9.

At 1415, the UE may determine whether the identified allocation ofuplink resources is canceled based on the uplink cancellationindication. The operations of 1415 may be performed according to themethods described herein. In some examples, aspects of the operations of1415 may be performed by an uplink cancellation manager as describedwith reference to FIGS. 6 through 9.

At 1420, the UE may perform uplink communications of either the firsttype of communications or the second type of communications based on thedetermining. The operations of 1420 may be performed according to themethods described herein. In some examples, aspects of the operations of1420 may be performed by an uplink communications manager as describedwith reference to FIGS. 6 through 9.

FIG. 15 shows a flowchart illustrating a method 1500 that supportsuplink transmission cancellation in accordance with aspects of thepresent disclosure. The operations of method 1500 may be implemented bya UE 115 or its components as described herein. For example, theoperations of method 1500 may be performed by a communication manager asdescribed with reference to FIGS. 6 through 9. In some examples, a UEmay execute a set of instructions to control the functional elements ofthe UE to perform the described functions. Additionally oralternatively, a UE may perform aspects of the described functions usingspecial-purpose hardware.

At 1505, the UE may identify an allocation of uplink resourcesassociated with a first type of communications with a first latencythreshold. The operations of 1505 may be performed according to themethods described herein. In some examples, aspects of the operations of1505 may be performed by an uplink allocation manager as described withreference to FIGS. 6 through 9.

At 1510, the UE may receive an uplink cancellation indication associatedwith a second type of communications with a second latency thresholdthat is different from the first latency threshold. The operations of1510 may be performed according to the methods described herein. In someexamples, aspects of the operations of 1510 may be performed by anuplink cancellation manager as described with reference to FIGS. 6through 9.

At 1515, the UE may determine whether the identified allocation ofuplink resources is canceled based on the uplink cancellationindication. The operations of 1515 may be performed according to themethods described herein. In some examples, aspects of the operations of1515 may be performed by an uplink cancellation manager as describedwith reference to FIGS. 6 through 9.

At 1520, the UE may receive an uplink grant after receiving the uplinkcancellation indication, the uplink grant including communicationresources associated with the uplink cancellation indication. Theoperations of 1520 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1520 may beperformed by an uplink allocation manager as described with reference toFIGS. 6 through 9.

At 1525, the UE may ignore at least a portion of the uplink cancellationindication based on receiving the uplink grant after receiving theuplink cancellation indication. The operations of 1525 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1525 may be performed by an uplink cancellationmanager as described with reference to FIGS. 6 through 9.

At 1530, the UE may perform uplink communications of either the firsttype of communications or the second type of communications based on thedetermining. The operations of 1530 may be performed according to themethods described herein. In some examples, aspects of the operations of1530 may be performed by an uplink communications manager as describedwith reference to FIGS. 6 through 9.

FIG. 16 shows a flowchart illustrating a method 1600 that supportsuplink transmission cancellation in accordance with aspects of thepresent disclosure. The operations of method 1600 may be implemented bya base station 105 or its components as described herein. For example,the operations of method 1600 may be performed by a communicationmanager as described with reference to FIGS. 10 through 13. In someexamples, a base station may execute a set of instructions to controlthe functional elements of the base station to perform the describedfunctions. Additionally or alternatively, a base station may performaspects of the described functions using special-purpose hardware.

At 1605, the base station may transmit an allocation of uplink resourcesassociated with a first type of communications with a first latencythreshold. The operations of 1605 may be performed according to themethods described herein. In some examples, aspects of the operations of1605 may be performed by an uplink allocation manager as described withreference to FIGS. 10 through 13.

At 1610, the base station may determine a reallocation of the uplinkresources based on a second type of communications with a second latencythreshold that is different from the first latency threshold. Theoperations of 1610 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1610 may beperformed by a reallocation manager as described with reference to FIGS.10 through 13.

At 1615, the base station may transmit an uplink cancellation indicationcorresponding to the uplink resources based on the determining. Theoperations of 1615 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1615 may beperformed by a cancellation indication manager as described withreference to FIGS. 10 through 13.

FIG. 17 shows a flowchart illustrating a method 1700 that supportsuplink transmission cancellation in accordance with aspects of thepresent disclosure. The operations of method 1700 may be implemented bya base station 105 or its components as described herein. For example,the operations of method 1700 may be performed by a communicationmanager as described with reference to FIGS. 10 through 13. In someexamples, a base station may execute a set of instructions to controlthe functional elements of the base station to perform the describedfunctions. Additionally or alternatively, a base station may performaspects of the described functions using special-purpose hardware.

At 1705, the base station may transmit an allocation of uplink resourcesassociated with a first type of communications with a first latencythreshold. The operations of 1705 may be performed according to themethods described herein. In some examples, aspects of the operations of1705 may be performed by an uplink allocation manager as described withreference to FIGS. 10 through 13.

At 1710, the base station may determine a reallocation of the uplinkresources based on a second type of communications with a second latencythreshold that is different from the first latency threshold. Theoperations of 1710 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1710 may beperformed by a reallocation manager as described with reference to FIGS.10 through 13.

At 1715, the base station may transmit an uplink cancellation indicationcorresponding to the uplink resources based on the determining. Theoperations of 1715 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1715 may beperformed by a cancellation indication manager as described withreference to FIGS. 10 through 13.

At 1720, the base station may transmit, to a UE, an uplink grantincluding communication resources associated with the uplinkcancellation indication, the uplink grant indicating to the UE to ignoreat least a portion of the uplink cancellation indication. The operationsof 1720 may be performed according to the methods described herein. Insome examples, aspects of the operations of 1720 may be performed by anuplink allocation manager as described with reference to FIGS. 10through 13.

It should be noted that the methods described herein describe possibleimplementations, and that the operations and the steps may be rearrangedor otherwise modified and that other implementations are possible.Further, aspects from two or more of the methods may be combined.

Techniques described herein may be used for various wirelesscommunications systems such as code division multiple access (CDMA),time division multiple access (TDMA), frequency division multiple access(FDMA), orthogonal frequency division multiple access (OFDMA), singlecarrier frequency division multiple access (SC-FDMA), and other systems.A CDMA system may implement a radio technology such as CDMA2000,Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000,IS-95, and IS-856 standards. IS-2000 Releases may be commonly referredto as CDMA2000 1×, 1×, etc. IS-856 (TIA-856) is commonly referred to asCDMA2000 1×EV-DO, High Rate Packet Data (HRPD), etc. UTRA includesWideband CDMA (WCDMA) and other variants of CDMA. A TDMA system mayimplement a radio technology such as Global System for MobileCommunications (GSM).

An OFDMA system may implement a radio technology such as Ultra MobileBroadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical andElectronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal MobileTelecommunications System (UMTS). LTE, LTE-A, and LTE-A Pro are releasesof UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Pro, NR,and GSM are described in documents from the organization named “3rdGeneration Partnership Project” (3GPP). CDMA2000 and UMB are describedin documents from an organization named “3rd Generation PartnershipProject 2” (3GPP2). The techniques described herein may be used for thesystems and radio technologies mentioned herein as well as other systemsand radio technologies. While aspects of an LTE, LTE-A, LTE-A Pro, or NRsystem may be described for purposes of example, and LTE, LTE-A, LTE-APro, or NR terminology may be used in much of the description, thetechniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro,or NR applications.

A macro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and may allow unrestricted access by UEswith service subscriptions with the network provider. A small cell maybe associated with a lower-powered base station, as compared with amacro cell, and a small cell may operate in the same or different (e.g.,licensed, unlicensed, etc.) frequency bands as macro cells. Small cellsmay include pico cells, femto cells, and micro cells according tovarious examples. A pico cell, for example, may cover a small geographicarea and may allow unrestricted access by UEs with service subscriptionswith the network provider. A femto cell may also cover a smallgeographic area (e.g., a home) and may provide restricted access by UEshaving an association with the femto cell (e.g., UEs in a closedsubscriber group (CSG), UEs for users in the home, and the like). An eNBfor a macro cell may be referred to as a macro eNB. An eNB for a smallcell may be referred to as a small cell eNB, a pico eNB, a femto eNB, ora home eNB. An eNB may support one or multiple (e.g., two, three, four,and the like) cells, and may also support communications using one ormultiple component carriers.

The wireless communications systems described herein may supportsynchronous or asynchronous operation. For synchronous operation, thebase stations may have similar frame timing, and transmissions fromdifferent base stations may be approximately aligned in time. Forasynchronous operation, the base stations may have different frametiming, and transmissions from different base stations may not bealigned in time. The techniques described herein may be used for eithersynchronous or asynchronous operations.

Information and signals described herein may be represented using any ofa variety of different technologies and techniques. For example, data,instructions, commands, information, signals, bits, symbols, and chipsthat may be referenced throughout the description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection withthe disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, an ASIC, an FPGA, or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described herein. A general-purpose processor may be amicroprocessor, but in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computing devices(e.g., a combination of a DSP and a microprocessor, multiplemicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, or any combination thereof. Software shall beconstrued broadly to mean instructions, instruction sets, code, codesegments, program code, programs, subprograms, software modules,applications, software applications, software packages, routines,subroutines, objects, executables, threads of execution, procedures,functions, etc., whether referred to as software, firmware, middleware,microcode, hardware description language, or otherwise. If implementedin software (e.g., executed by a processor), the functions may be storedon or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described herein can be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations.

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that can beaccessed by a general purpose or special purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media mayinclude RAM, ROM, electrically erasable programmable ROM (EEPROM), flashmemory, compact disk (CD) ROM or other optical disk storage, magneticdisk storage or other magnetic storage devices, or any othernon-transitory medium that can be used to carry or store desired programcode means in the form of instructions or data structures and that canbe accessed by a general-purpose or special-purpose computer, or ageneral-purpose or special-purpose processor. Also, any connection isproperly termed a computer-readable medium. For example, if the softwareis transmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,include CD, laser disc, optical disc, digital versatile disc (DVD),floppy disk and Blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

As used herein, including in the claims, “or” as used in a list of items(e.g., a list of items prefaced by a phrase such as “at least one of” or“one or more of”) indicates an inclusive list such that, for example, alist of at least one of A, B, or C means A or B or C or AB or AC or BCor ABC (i.e., A and B and C). Also, as used herein, the phrase “basedon” shall not be construed as a reference to a closed set of conditions.For example, an exemplary step that is described as “based on conditionA” may be based on both a condition A and a condition B withoutdeparting from the scope of the present disclosure. In other words, asused herein, the phrase “based on” shall be construed in the same manneras the phrase “based at least in part on.” As used herein, the term“and/or,” when used in a list of two or more items, means that any oneof the listed items can be employed by itself, or any combination of twoor more of the listed items can be employed. For example, if acomposition is described as containing components A, B, and/or C, thecomposition can contain A alone; B alone; C alone; A and B incombination; A and C in combination; B and C in combination; or A, B,and C in combination.

In the appended figures, similar components or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label, or othersubsequent reference label.

The description set forth herein, in connection with the appendeddrawings, describes example configurations and does not represent allthe examples that may be implemented or that are within the scope of theclaims. The term “exemplary” used herein means “serving as an example,instance, or illustration,” and not “preferred” or “advantageous overother examples.” The detailed description includes specific details forthe purpose of providing an understanding of the described techniques.These techniques, however, may be practiced without these specificdetails. In some instances, well-known structures and devices are shownin block diagram form in order to avoid obscuring the concepts of thedescribed examples.

The description herein is provided to enable a person skilled in the artto make or use the disclosure. Various modifications to the disclosurewill be readily apparent to those skilled in the art, and the genericprinciples defined herein may be applied to other variations withoutdeparting from the scope of the disclosure. Thus, the disclosure is notlimited to the examples and designs described herein, but is to beaccorded the broadest scope consistent with the principles and novelfeatures disclosed herein.

What is claimed is:
 1. A method for wireless communications at a networkentity, the method comprising: outputting an allocation of uplinkresources associated with a first type of communications with a firstlatency threshold; determining a reallocation of the uplink resourcesbased at least in part on a second type of communications with a secondlatency threshold that is different from the first latency threshold;and outputting an uplink cancellation indication corresponding to theuplink resources based at least in part on the determining.
 2. Themethod of claim 1, further comprising: generating a bitmap associatedwith a set of communication resources in the time domain and frequencydomain, each bit of the bitmap corresponding to a respective subset ofthe communication resources, and each bit indicating whether or notcancellation applies to the respective subset of the communicationresources, wherein outputting the uplink cancellation indicationcomprises outputting the bitmap.
 3. The method of claim 2, wherein thebitmap corresponds to a configured uplink bandwidth part.
 4. The methodof claim 2, wherein outputting the uplink cancellation indicationcomprises: outputting a repetition indicator associated with the bitmap.5. The method of claim 2, wherein the respective subset of thecommunication resources corresponding to each bit of the bitmapcorresponds to uplink resources of an uplink/downlink TDD configuration.6. The method of claim 1, wherein determining the reallocation ofresources comprises: determining a time for applying cancellation basedat least in part on a time of transmitting the uplink cancellationindication and a configured time offset for cancellation.
 7. The methodof claim 6, wherein the configured time offset for cancellation is basedat least in part on a user equipment (UE) capability.
 8. The method ofclaim 6, wherein determining the time for applying cancellation is basedat least in part on an uplink/downlink time division duplex (TDD)configuration.
 9. The method of claim 1, further comprising: outputtingan uplink grant comprising communication resources associated with theuplink cancellation indication, the uplink grant indicating to the UE toignore at least a portion of the uplink cancellation indication.
 10. Themethod of claim 9, wherein the uplink grant is associated with thesecond type of communications, and the indication to the UE to ignore atleast a portion of the uplink cancellation indication is based at leastin part on the uplink grant being associated with the second type ofcommunications.
 11. The method of claim 9, wherein the uplink grant isassociated with a type of physical channel, and the indication to the UEto ignore at least a portion of the uplink cancellation indication isbased at least in part on the type of physical channel.
 12. An apparatuscomprising: a processor, memory coupled to the processor, andinstructions stored in the memory and executable by the processor tocause the apparatus to: output an allocation of uplink resourcesassociated with a first type of communications with a first latencythreshold; determine a reallocation of the uplink resources based atleast in part on a second type of communications with a second latencythreshold that is different from the first latency threshold; and outputan uplink cancellation indication corresponding to the uplink resourcesbased at least in part on the determining.
 13. The apparatus of claim12, wherein the instructions are further executable by the processor tocause the apparatus to: generate a bitmap associated with a set ofcommunication resources in the time domain and frequency domain, eachbit of the bitmap corresponding to a respective subset of thecommunication resources, and each bit indicating whether or notcancellation applies to the respective subset of the communicationresources, wherein the instructions to output the uplink cancellationindication comprise instructions executable by the processor to outputthe bitmap.
 14. The apparatus of claim 13, wherein the bitmapcorresponds to a configured uplink bandwidth part.
 15. The apparatus ofclaim 13, wherein the instructions to output the uplink cancellationindication comprise instructions executable by the processor to causethe apparatus to: output a repetition indicator associated with thebitmap.
 16. The apparatus of claim 13, wherein the respective subset ofthe communication resources corresponding to each bit of the bitmapcorresponds to uplink resources of an uplink/downlink TDD configuration.17. The apparatus of claim 12, wherein the instructions to determine thereallocation of resources comprises instructions executable by theprocessor to: determine a time for applying cancellation based at leastin part on a time of transmitting the uplink cancellation indication anda configured time offset for cancellation.
 18. The apparatus of claim17, wherein the configured time offset for cancellation is based atleast in part on a user equipment (UE) capability.
 19. The apparatus ofclaim 17, wherein the instructions to determine the time for applyingcancellation is based at least in part on an uplink/downlink timedivision duplex (TDD) configuration.
 20. The apparatus of claim 12,wherein the instructions are further executable by the processor tocause the apparatus to: output an uplink grant comprising communicationresources associated with the uplink cancellation indication, the uplinkgrant indicating to the UE to ignore at least a portion of the uplinkcancellation indication.
 21. The apparatus of claim 20, wherein theuplink grant is associated with the second type of communications, andthe indication to the UE to ignore at least a portion of the uplinkcancellation indication is based at least in part on the uplink grantbeing associated with the second type of communications.
 22. Theapparatus of claim 20, wherein the uplink grant is associated with atype of physical channel, and the indication to the UE to ignore atleast a portion of the uplink cancellation indication is based at leastin part on the type of physical channel.
 23. An apparatus comprising:means for outputting an allocation of uplink resources associated with afirst type of communications with a first latency threshold; means fordetermining a reallocation of the uplink resources based at least inpart on a second type of communications with a second latency thresholdthat is different from the first latency threshold; and means foroutputting an uplink cancellation indication corresponding to the uplinkresources based at least in part on the determining.
 24. Anon-transitory computer-readable medium storing code for wirelesscommunication at a network entity, the code comprising instructionsexecutable by a processor to: output an allocation of uplink resourcesassociated with a first type of communications with a first latencythreshold; determine a reallocation of the uplink resources based atleast in part on a second type of communications with a second latencythreshold that is different from the first latency threshold; and outputan uplink cancellation indication corresponding to the uplink resourcesbased at least in part on the determining.